> It sounds like your use case really wants a %iftoken,
something that can
> tell you if something is a single pasteable token or
not.
Hehe, funny that you mention that -- I did add %IFTOK0
and %IFTOK1 in NASM64: check for exactly zero or one
tokens.
But back to %IFNUM.
Don't get me wrong -- there are times when accepting a
sign as part of a number is the desired behavior. But the
only one who can tell, is the user.
I kinda hate to suggest it... but perhaps this one of those
few times were a user-selectable option is needed?
I already had to deal with that for two things in NASM64:
expand certain tokens before/after listing them, as well
as looking up context-local definitions in outer contexts.
As a result, I added %OPTION [-|+]EXPAND, as well as
%OPTION [-|+]LOOKUP -- perhaps %IFNUM requires a
new %OPTION [-|+]SIGNED or such...?
------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
a>
_______________________________________________
Nasm-devel mailing list
Nasm-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nasm-devel
a>
|