Hi,

after many hours trying to locate a bug, I think
the bug is in fasm's macros,

if you compile bug1.asm and run it,

it wrongly echoes 'b'

but if you change

rx__ equ ax

to

rx__ equ bx

it now correctly echoes 'a'

I think this is a bug because if you study the code
you will see the read__ macro ignores rx__ as
rx__ is only used if an argument is non register,

so changing rx__ shouldnt change anything in this example,

or have I misunderstood something?

You should define "registers__" this way:

or, even better, using "define".
The macroinstructions are like instruction mnemonics, they are recognized only when in beginning of the line (not counting the initial colon-followed labels). Each macroinstruction with its parameters spans the entire line and generates the full lines as its result - it cannot be used like symbolic constants.

ok,

I tried that and it functioned,

I have to look at the other macros I'm using.

can you make fasm give an error message for
the wrong usage I tried?


(the example I uploaded shouldnt have had the
"include fasm.i", so delete that )

It's not really the wrong usage, you can have both the "registers__" macro and "registers__" symbolic constant at the same time, so assembler is not able to tell whether it was what you intended or not.

yeah, but defining "registers__" after a macro via equ is not possible because macroinstruction is processed before equ.. you have to use define:


and when you use restore it goes back to macroinstruction.