public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/8270: back-slash newline extension can't be removed
Date: Tue, 22 Oct 2002 14:26:00 -0000 [thread overview]
Message-ID: <20021022212600.5877.qmail@sources.redhat.com> (raw)
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
next reply other threads:[~2002-10-22 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 14:26 Zack Weinberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-22 14:23 neil
2002-10-21 13:06 Neil Booth
2002-10-17 15:26 eschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021022212600.5877.qmail@sources.redhat.com \
--to=zack@codesourcery.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).