bug-bison
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 1.75 test suite failure with HP-UX C compiler and #endif


From: Albert Chin-A-Young
Subject: Re: 1.75 test suite failure with HP-UX C compiler and #endif
Date: Wed, 13 Nov 2002 18:05:35 -0600
User-agent: Mutt/1.2.5i

On Wed, Nov 13, 2002 at 03:47:17PM -0800, Paul Eggert wrote:
> > From: Albert Chin-A-Young <address@hidden>
> > Date: Wed, 13 Nov 2002 14:48:42 -0600
> > 
> > (HP-UX 10.20, 11.00, 11i)...
> > 4. input.at:93: testing Torturing the Scanner...
> > input.at:206: bison -d -v -o input.c input.y
> > input.at:207: $CC $CFLAGS $CPPFLAGS input.c main.c -o input
> > stderr:
> > cpp: "input.y", line 96: error 4033: Missing #endif at end of file.
> 
> Perhaps this is due to a bug in the HP-UX C compiler?
> What does it do with the following text?
> 
> #ifdef __STDC__
> /\
> * A comment with backslash-newlines in it. %{ %} *\
> \
> /
> char str[] = "\\
> " A string with backslash-newlines in it %{ %} \\
> "";
> char apostrophe = '\\
> \
> '\
> ';
> #endif
> 
> Assuming the HP-UX compiler mishandles the above example, is there a
> simple way to avoid the compiler bug?  For example, perhaps we could
> remove the lines that contain solitary backslashes?

$ cc -c b.c
cpp: "b.c", line 13: error 4048: Non-terminating comment at end of file.
cpp: "b.c", line 13: error 4033: Missing #endif at end of file.

Removing the lines with solitary backslashes solves the problem.

-- 
albert chin (address@hidden)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]