Re: gcc cannot recognize 0xe+0x1

2009-03-02 Thread Andreas Schwab
Tadahito Kobayashi koval...@gmail.com writes: return 0xe+0x1 ; 0xe+0x1 forms a single preprocessing token (a pp-number), but cannot be converted to a valid token. Add some whitespace around + to break up the preprocessing token. Andreas. -- Andreas Schwab, sch...@linux-m68k.org Key

Re: gcc cannot recognize 0xe+0x1

2009-03-02 Thread Tadahito Kobayashi
Understood, That's a single token according to the definition of pp-number. It's not a bug. Thanks for kindly teaching. -Kovaltan

gcc cannot recognize 0xe+0x1

2009-03-01 Thread Tadahito Kobayashi
Is this a known bug? It looks like gcc treats +0x1 as a floating suffix. I confirmed this on cygwin at winXP. ### $ cat test.c int main(int argc, char* argv[]) { return 0xe+0x1 ; } $ gcc test.c test.c:4:9: invalid suffix