Using %unmacro on a macro that currently executes appears to work fine, but I expect that it might cause NASM to segfault in some cases. A %warning inside such a non-existing macro (ie. behind the %unmacro that removed this macro) will display an empty string for the current macro's name. (Both tested with NASM 2.10rc1, Win32.) The request concerns documenting the current behaviour (ie. that it is allowed to use %unmacro for a currently executing macro), and if necessary improving NASM's behaviour so that it will not segfault in this situation; or additionally improving NASM's behaviour here in other ways.
Log in to post a comment.