public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: eschmidt@safeaccess.com To: gcc-gnats@gcc.gnu.org Subject: preprocessor/8270: back-slash newline extension can't be removed Date: Thu, 17 Oct 2002 15:26:00 -0000 [thread overview] Message-ID: <20021017221751.2533.qmail@sources.redhat.com> (raw) >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:
next reply other threads:[~2002-10-17 22:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-17 15:26 eschmidt [this message] 2002-10-21 13:06 Neil Booth 2002-10-22 14:23 neil 2002-10-22 14:26 Zack Weinberg
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=20021017221751.2533.qmail@sources.redhat.com \ --to=eschmidt@safeaccess.com \ --cc=gcc-gnats@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: linkBe 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).