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: Joe Buck <Joe dot Buck at synopsys dot COM>
To: Mike Stump <mrs at apple dot com>
Cc: Howard Hinnant <howard dot hinnant at gmail dot com>, gcc at gcc dot gnu dot org
Date: Tue, 25 Oct 2005 21:25:03 -0700
Subject: Re: backslash whitespace newline
References: <200510252222.j9PMMMiU024597@earth.phy.uc.edu> <5540C4F2-6E4B-4684-AA7F-2D206D81D2BF@twcny.rr.com> <20051026001152.GJ18194@synopsys.com> <72FD8F0C-DF86-44D5-ABF3-8FED7BCD59D4@apple.com>

On Tue, Oct 25, 2005 at 06:45:55PM -0700, Mike Stump wrote:
> On Oct 25, 2005, at 5:11 PM, Joe Buck wrote:
> >I personally like the fact that gcc's behavior does not depend on  
> >invisible characters
> 
> All other things being equal, this is a nice design goal.  I like it  
> too.  Should we break peoples otherwise portable code to have an  
> implementation defined behavior that no one else has?

Code that depends on invisible whitespace to function correctly is
already broken.  At some point, someone will do the equivalent of
delete-trailing-whitespace and break it.

And the code is easily cleaned up.

Follow-Ups:
- Re: backslash whitespace newline
  - From: Vincent Lefevre

References:
- Re: backslash whitespace newline
  - From: Andrew Pinski
- Re: backslash whitespace newline
  - From: Howard Hinnant
- Re: backslash whitespace newline
  - From: Joe Buck
- Re: backslash whitespace newline
  - From: Mike Stump

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