Re: [Nasm-devel] [nasm:master] BR30730640: Restore preprocessor token concatenation rules

[H. P. A. <hp...@zy...>]

On 10/01/2010 03:09 AM, anonymous coward wrote:
> 
> I think I now understand why TOK_FLOAT was introduced -- so
> that TOKEN_FLOAT can be handed to evaluate(). (I went down
> a different path for this functionality -- instead of eval ops I did it
> as special-cased pp smacs -- so I didn't need TOK_FLOAT.)
> 
> Thanks to this TOK_FLOAT complexity hpa's "use tokenize()"
> seems like your best bet. (And, as a side effect, you'd get the
> desired symmetry between implicit (mmac) and explicit (%+)
> concatenation.)
> 

It's worth noting that you can run into trouble even without TOK_FLOAT
-- it's fairly easy to construct situations where concatenated tokens
just won't work as-is.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.