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: Andrew Pinski <pinskia at physics dot uc dot edu>
Cc: Joe dot Buck at synopsys dot COM (Joe Buck), ssen at opendarwin dot org (Shantonu Sen), gcc at gcc dot gnu dot org (GCC Development)
Date: Wed, 26 Oct 2005 09:29:48 -0700
Subject: Re: backslash whitespace newline
References: <200510260605.j9Q65xVK001172@earth.phy.uc.edu>

On Oct 25, 2005, at 11:05 PM, Andrew Pinski wrote:

Why did Apple revert that patch, well because there was push back from
internal developers who did not want to fix their code.  Why should
this case be any difference?

I'm sorry you don't understand the differences. In one, we have every expectation that the code will compile on every C++ compiler out there, except for gcc, and that makes it a gcc bug that has been fixed. The other is a gcc feature that causes code that does compile on every other C++ compiler that I know about to not compile on gcc, so I guess you're right after all, there is no difference, we'd call it a bug that needs to be fixed. :-) Wait, what side were you arguing? :-)

or even worse fork GCC.

Is this like calling someone a Nazi?

References:
- Re: backslash whitespace newline
  - From: Andrew Pinski

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