The idea for variable.inc file is great in order to help those porting FASM.
There is only one problem, that initialized and initialized variables are defined in one file.
This prevents direct using of the file for ports that use some other placing of data. Particularly, Fresh uses "uglobal" and "iglobal" macroses for defining uninitialized and initialized data variables. So I can't simply use variables.inc this way:


The same will happen if for example someone want to use separate sections for initialized and uninitialized variables.

Possible solutions:
1. separate uninitialized and initialized variables in two different include files, thus allowing using it like this:


2. As far as there is only one initialized variable (locals_counter) - it is possible to make it uninitialized and leave the initialization to the interface.

Regards

Why don't you change all the '?' in variable.inc to '0' thereby
initialising all the variables to zero?

I always initialise my variables.

Cheers,
Alan

He could do this, but this would require additional executable size.

Another solution I would suggest is to simply separate the "variables.inc" in an "iglobal" and an "uglobal" block (both in the same file) which will actually be placed into the executable in the main Fasm.asm or Fresh.asm file.

Alan Illeman, actually Windows zeroes undefined variables. Sometimes, it is not very usefull to initialize the variables, because its value is not known at the design time, but have to be computed in run time.

Actually in the latest FASM 1.60, mentioned problem is solved, so...

Regards.