From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10381 invoked by alias); 21 Oct 2002 20:06:03 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 10366 invoked by uid 71); 21 Oct 2002 20:06:03 -0000 Date: Mon, 21 Oct 2002 13:06:00 -0000 Message-ID: <20021021200603.10365.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Neil Booth Subject: Re: preprocessor/8270: back-slash newline extension can't be removed Reply-To: Neil Booth X-SW-Source: 2002-10/txt/msg00789.txt.bz2 List-Id: The following reply was made to PR preprocessor/8270; it has been noted by GNATS. From: Neil Booth To: eschmidt@safeaccess.com, Zack Weinberg 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.