(j3.2006) (j3.2005) Re: question on token replacement/concatenation

[Aleksandar Donev]

Hi,

Happy new year to everyone. Finally some time to write a paper on this:

Malcolm Cohen wrote:
> So, the question is, how do we resolve the ambiguous parse?
> You would prefer to restrict the user.  Me, I'd rather resolve
> the parse with a constraint on macro-actual-arg-value, viz
>   If the first two tokens of <basic-token-sequence> are a <name> and an
>   equals sign, the <name> shall not be the same as that of a dummy argument
>   of the macro being expanded.
I've put my preferred solution in the attached paper. Needless to say, 
it is not the same as the above, imo, "quick and dirty fix".

Best,
Aleks

-- 
Aleksandar Donev, Ph.D.
Lawrence Postdoctoral Fellow @ LLNL
High Performance Computational Materials Science and Chemistry
E-mail: donev1 at llnl.gov
Phone: (925) 424-6816  Fax: (925) 423-0785
Address: P.O.Box 808, L-367, Livermore, CA 94551-9900
Web: http://cherrypit.princeton.edu/donev
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: MacroEquals.txt
Url: http://j3.scs.gmu.edu/pipermail/j3/attachments/20070102/3141e7dd/attachment.txt