This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: backslash whitespace newline

From: Robert Dewar <dewar at adacore dot com>
To: Dale Johannesen <dalej at apple dot com>
Cc: Joe Buck <Joe dot Buck at synopsys dot COM>, gcc at gcc dot gnu dot org, Andrew Pinski <pinskia at physics dot uc dot edu>,Howard Hinnant <howard dot hinnant at gmail dot com>
Date: Wed, 26 Oct 2005 13:22:48 -0400
Subject: Re: backslash whitespace newline
References: <54875567-6ED9-44F2-A631-76C2E3E3B6DA@twcny.rr.com> <200510260022.j9Q0MCWW027243@earth.phy.uc.edu> <20051026004056.GL18194@synopsys.com> <cedde691e721248a5a03d7c1af5e2b66@apple.com>

Dale Johannesen wrote:

Yes.  From the user's point of view, the best thing appears to be
treating backslashes in C++ comments as part of the comment,
regardless of what follows them; that seems to follow the principle
of least surprise. That's not standard conforming, and therefore I'm
not advocating it for gcc, but it probably wouldn't break anything
outside compiler testsuites.  Maybe this treatment should be made
standard conforming...?


I agree this would be a far preferable definition, allowing comments
to be continued with a \ seems a truly silly feature.

References:
- Re: backslash whitespace newline
  - From: Howard Hinnant
- Re: backslash whitespace newline
  - From: Andrew Pinski
- Re: backslash whitespace newline
  - From: Joe Buck
- Re: backslash whitespace newline
  - From: Dale Johannesen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]