public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: preprocessor/8270: back-slash newline extension can't be removed
@ 2002-10-21 13:06 Neil Booth
0 siblings, 0 replies; 4+ messages in thread
From: Neil Booth @ 2002-10-21 13:06 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR preprocessor/8270; it has been noted by GNATS.
From: Neil Booth <neil@daikokuya.co.uk>
To: eschmidt@safeaccess.com, Zack Weinberg <zack@codesourcery.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: preprocessor/8270: back-slash newline extension can't be removed
Date: Mon, 21 Oct 2002 20:57:43 +0100
eschmidt@safeaccess.com wrote:-
> >Synopsis: back-slash newline extension can't be removed
[...]
> The preprocessor does not remove the extension allowing extra white space in a backslash-newline, even when GCC is invoked with -ansi
>
> gcc -ansi bug.c -o bug
>
> bug.c:1:13: warning: backslash and newline separated by space
> bug.c:3: parse error before "return"
>
> An executable file sohuld have been created.
Zack, I favour closing this, since the behaviour can be avoided if
deemed necessary by judicious insertion of a C comment. Agreed?
Neil.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: preprocessor/8270: back-slash newline extension can't be removed
@ 2002-10-22 14:26 Zack Weinberg
0 siblings, 0 replies; 4+ messages in thread
From: Zack Weinberg @ 2002-10-22 14:26 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR preprocessor/8270; it has been noted by GNATS.
From: Zack Weinberg <zack@codesourcery.com>
To: Neil Booth <neil@daikokuya.co.uk>
Cc: eschmidt@safeaccess.com, gcc-gnats@gcc.gnu.org
Subject: Re: preprocessor/8270: back-slash newline extension can't be removed
Date: Tue, 22 Oct 2002 14:19:04 -0700
On Mon, Oct 21, 2002 at 08:57:43PM +0100, Neil Booth wrote:
> eschmidt@safeaccess.com wrote:-
>
> > >Synopsis: back-slash newline extension can't be removed
>
> [...]
>
> > The preprocessor does not remove the extension allowing extra white space in a backslash-newline, even when GCC is invoked with -ansi
> >
> > gcc -ansi bug.c -o bug
> >
> > bug.c:1:13: warning: backslash and newline separated by space
> > bug.c:3: parse error before "return"
> >
> > An executable file sohuld have been created.
>
> Zack, I favour closing this, since the behaviour can be avoided if
> deemed necessary by judicious insertion of a C comment. Agreed?
Agreed. I don't consider it necessary to cut any slack for people
whose code depends on trailing whitespace.
zw
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: preprocessor/8270: back-slash newline extension can't be removed
@ 2002-10-22 14:23 neil
0 siblings, 0 replies; 4+ messages in thread
From: neil @ 2002-10-22 14:23 UTC (permalink / raw)
To: eschmidt, gcc-bugs, gcc-prs, nobody
Synopsis: back-slash newline extension can't be removed
State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Tue Oct 22 14:23:58 2002
State-Changed-Why:
We feel that in the rare cases where a backslash newline is not intended, a C-style comment can be inserted.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8270
^ permalink raw reply [flat|nested] 4+ messages in thread
* preprocessor/8270: back-slash newline extension can't be removed
@ 2002-10-17 15:26 eschmidt
0 siblings, 0 replies; 4+ messages in thread
From: eschmidt @ 2002-10-17 15:26 UTC (permalink / raw)
To: gcc-gnats
>Number: 8270
>Category: preprocessor
>Synopsis: back-slash newline extension can't be removed
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: rejects-legal
>Submitter-Id: net
>Arrival-Date: Thu Oct 17 15:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: eschmidt@safeaccess.com
>Release: gcc 3.2
>Organization:
>Environment:
Configured with: /devel/gcc32/gnu/gcc-3.2/configure i586-pc-msdosdjgpp --prefix=/dev/env/DJDIR --disable-nls
Thread model: single
>Description:
The preprocessor does not remove the extension allowing extra white space in a backslash-newline, even when GCC is invoked with -ansi
gcc -ansi bug.c -o bug
bug.c:1:13: warning: backslash and newline separated by space
bug.c:3: parse error before "return"
An executable file sohuld have been created.
>How-To-Repeat:
#define foo \
int main(void) {
return 0;
}
>Fix:
Workaround: put a comment between the backslash and the newline.
>Release-Note:
>Audit-Trail:
>Unformatted:
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-10-22 21:26 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-21 13:06 preprocessor/8270: back-slash newline extension can't be removed Neil Booth
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 14:26 Zack Weinberg
2002-10-22 14:23 neil
2002-10-17 15:26 eschmidt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).