[Nasm-devel] [Bug 3392716] Macro expansion behaviour

Igor Munkin imun at cpan.org
Thu Dec 10 05:01:05 PST 2020


On 10.12.20, hpa at zytor.com wrote:


> I think we're should simply disallow undefining or redefining a macro
> that is in the process of being expanded. We have that information as
> we tag all the macros we have descended through.

Thanks, I believe I get it.

> I think this can be an error and the %unmacro dropped with a
> nasm_nonfatal() error message.

In other words, such %unmacro should be considered as nop, shouldn't it?

> -- 
> Sent from my Android device with K-9 Mail. Please excuse my brevity.

Best regards,

More information about the Nasm-devel mailing list