unexpected parse error in #define

Zack Weinberg zackw@stanford.edu
Thu Oct 5 20:23:00 GMT 2000


On Thu, Oct 05, 2000 at 08:06:11PM -0700, Erik Talvola wrote:
> I wouldn't normally expect that continuations lines
> would be treated differently when using #define with a
> macro that takes arguments vs. one which doesn't. 
> Didn't see anything in the CPP manual which describes
> this, but don't have a copy of the ANSI standard to
> know whether this is specified or not:
> 
> [etalvo@hobo etalvo]$ more test.c
> 
> #define FOO a \
>  { a(); }
> 
> [etalvo@hobo etalvo]$ more test3.c
> 
> #define FOO(r) a \
>  { a(); }
> 
> [etalvo@hobo etalvo]$ gcc -c test.c
> test.c:3: parse error before `{'
> [etalvo@hobo etalvo]$ gcc -c test3.c
> [etalvo@hobo etalvo]$

The odds are overwhelming that the actual problem is that there's a
space at the end of line 2 of test.c.  In all released versions of
GCC, \-newline doesn't trigger continuation if there's whitespace
between the \ and the end of the line.

We recently discussed changing this but I don't remember if it was
implemented or not.

zw


More information about the Gcc-bugs mailing list