This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: backslash whitespace newline
- From: Andrew Pinski <pinskia at physics dot uc dot edu>
- To: pinskia at physics dot uc dot edu (Andrew Pinski)
- Cc: echristo at apple dot com (Eric Christopher), howard dot hinnant at gmail dot com (Howard Hinnant), gcc at gcc dot gnu dot org, joseph at codesourcery dot com, neil at daikokuya dot co dot uk (Neil Booth)
- Date: Tue, 25 Oct 2005 18:33:42 -0400 (EDT)
- Subject: Re: backslash whitespace newline
>
> >
> >
> > On Oct 24, 2005, at 3:52 PM, Neil Booth wrote:
> >
> > > Howard Hinnant wrote:-
> > >
> > >> I've been reviewing the age-old issue of interpreting
> > >> <whitespace>*<newline> as the end-of-line indicator as is the current
> > >> practice with gcc.
> > >
> > > FWIW I support abandoning this behaviour too.
> >
> > I filed bugzilla 24531 about this.
>
> Note this is documented behavior and I don't think we should change it at
> all since it is one more thing to break old gcc code like stuff in Linux kernel.
>
> We have people already complaining about removing extensions. Why should we change
> this implementionation defined documented behavior.
Oh, one more thing. This seems like the normal problem of not reading the docs
if something does not work the way you want it to work.
The only thing we can do is point it out that it is documented behavior and
then move on to the next issue. Also why are we discussing this when
there are more important bugs to fix currently as this behavior has been documented
for a long time, at least 4 years.
-- Pinski