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: Mike Stump <mrs at apple dot com>
To: Joe Buck <Joe dot Buck at synopsys dot COM>
Cc: Stan Shebs <shebs at apple dot com>, Andrew Pinski <pinskia at physics dot uc dot edu>, Eric Christopher <echristo at apple dot com>, Howard Hinnant <howard dot hinnant at gmail dot com>, gcc at gcc dot gnu dot org, joseph at codesourcery dot com, Neil Booth <neil at daikokuya dot co dot uk>
Date: Tue, 25 Oct 2005 18:37:18 -0700
Subject: Re: backslash whitespace newline
References: <200510252244.j9PMic4l025068@earth.phy.uc.edu> <435EBA53.5060805@apple.com> <20051025232546.GH18194@synopsys.com>

On Oct 25, 2005, at 4:25 PM, Joe Buck wrote:

I'm having a hard time picturing source code that

 a) exhibits different behavior because of this bug, and
 b) is maintainable (remember, the behavior depends on the presence
    of characters that are completely invisible to many tools).

Perhaps you could explain (without violating the customer's
confidentiality) how it is that this is an important problem?

Existing ASCII line art in documentation embedded in the source code as C++ style comments.

Follow-Ups:
- Re: backslash whitespace newline
  - From: Andrew Pinski

References:
- Re: backslash whitespace newline
  - From: Andrew Pinski
- Re: backslash whitespace newline
  - From: Stan Shebs
- Re: backslash whitespace newline
  - From: Joe Buck

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