Re: Possible bug in preprocessor

2007-04-10 Thread Richard Smith
Jim Wilson wrote: > JoseD wrote: > > @James > > What do you mean by 16.3.3/3? GCC's version ? > > This is a reference to the ISO C standard. No. It's a reference to the ISO C++ standard. 16.3.3/3 includes the sentence "If the result [of the ## operator] is not a valid preprocessing token, the

Re: Possible bug in preprocessor

2007-04-09 Thread Jim Wilson
JoseD wrote: @James What do you mean by 16.3.3/3? GCC's version ? This is a reference to the ISO C standard. Still don't see what the problem whith 2 tokens is... The problem is the fact that they are 2 tokens. You can do a ## b to create ab, but you can not do a ## ( to create a( becaus

Re: Possible bug in preprocessor

2007-04-03 Thread JoseD
e that there doesn't seem to be a consistent preprocessor spec. -- View this message in context: http://www.nabble.com/Possible-bug-in-preprocessor-tf3494353.html#a9827482 Sent from the gcc - Dev mailing list archive at Nabble.com.

Re: Possible bug in preprocessor

2007-03-30 Thread James Dennett
JoseD wrote: > Hi. Just wanted to share that the following macro gives an error on latest > versions of GCC, but is reported to work on 2.95.3 (tested on MorphOS but > should be the same for other OSses of course). > Both an old version of SASC(AmigaOS) and Borland (on X86) worked fine. > > #inclu

Re: Possible bug in preprocessor

2007-03-30 Thread Null Heart
a, b) a, b int main (int argc, char **argv) { printf("%s %s\n", GETBRCKTELMNT((YYY, XXX))); getchar(); return (0); } Regs Jose -- View this message in context: http://www.nabble.com/Possible-bug-in-preprocessor-tf3494353.html#a9760061 Sent from the gcc - Dev mailing list archive at Nabble.com.

Possible bug in preprocessor

2007-03-30 Thread JoseD
((YYY, XXX))); getchar(); return (0); } Regs Jose -- View this message in context: http://www.nabble.com/Possible-bug-in-preprocessor-tf3494353.html#a9760061 Sent from the gcc - Dev mailing list archive at Nabble.com.