millfork

Millfork: a middle-level programming language targeting 6502- and Z80-based microcomputers and home consoles

This project is maintained by KarolS

< back to index

Variable storage

Variables in Millfork can belong to one of the following storage classes:

Variables can also belong to one of the following memory areas (unless overridden with the @ operator):

All arrays can be considered static.

Static variables

Static variables have a fixed and unique memory location. Their lifetime is for the entire runtime of the program. If they do not have initial value declared, reading them before initialization yields an undefined value.

Stack variables

Stack variables, as their name suggests, live on the stack. Their lifetime starts with the beginning of the function they’re in and ends when the function returns. They are not automatically initialized before reading, reading them before initialization yields an undefined value. The main advantage is that they are perfectly safe to use in reentrant code, but the main disadvantages are:

The implementation depends on the target architecture:

Automatic variables

Automatic variables have lifetime starting with the beginning of the function they’re in and ending when the function returns. Most automatic variables reside in memory. They can share their memory location with other automatic variables and parameters, to conserve memory usage. They are not automatically initialized before reading, reading them before initialization yields an undefined value. Automatic local variables are not safe to use with reentrant functions, see the relevant documentation for more details.

Some small automatic variables may be inlined to registers. On 6502-like architectures, only 1-byte variables may be inlined. On 8080-like architectures, 1-byte and 2-byte variables may be inlined.

Automatic variables defined with the register keyword will have the priority when it comes to register allocation.

Parameters

Function parameters have lifetime starting with the beginning of the function call to the function they’re defined in and ending when the function returns. They reside in memory and can share their memory location with other parameters and automatic variables, to conserve memory usage. Unlike automatic variables, they are almost never inlined into registers. Parameters are not safe to use with reentrant functions, see the relevant documentation for more details.