Text macro was used before definition - is this necessary ?
Brought to you by:
japheth
Is the warning "Text macro was used before definition" really necessary ? Is there any case where something unexpected is done ? If not then perhaps you should consider removing this warning altogether. MASM doesn't seem to have an equivalent of this warning.
Also in the readme:
- 'Text macro was used before definition': this is a warning only.
However, using text macros before they have been defined will force
JWasm to do a full second path, which increases assembly time.
Shouldn't that say "a full second PASS"
> Is the warning "Text macro was used before definition" really necessary ?
An interesting philosophically question! I guess it is - at the very least - necessary for my aesthetic feelings.
And it might also be possible that using text macros before they are defined may cause problems for the "preprocessor listing" which is emitted with the -EP option.
Finally, since macros and macro functions can also not be used before they are defined, it's a - maybe strange - kind of justice and fairness.
> Shouldn't that say "a full second PASS"
Yes, definitely! Thanks, this will be fixed!