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: C Code mutilation by using gcc-3.3.x

From: Mike Stump <mrs at apple dot com>
To: "Robert M. Stockmann" <stock at stokkie dot net>
Cc: gcc at gcc dot gnu dot org, Linus Torvalds <torvalds at osdl dot org>, Dennis Ritchie <dmr at bell-labs dot com>, "Theodore Ts'o" <tytso at mit dot edu>, "H.J. Lu" <hjl at gnu dot ai dot mit dot edu>, "Eric S. Raymond" <esr at thyrsus dot com>, Alan Cox <alan at lxorguk dot ukuu dot org dot uk>
Date: Wed, 4 Feb 2004 12:28:52 -0800
Subject: Re: C Code mutilation by using gcc-3.3.x

On Wednesday, February 4, 2004, at 12:01 PM, Robert M. Stockmann wrote:

I write this email not by accident. I have emailed the below example to
several people and without exception stated that whats happening here
is a bad thing.

Yes, it is.

Whats going on here?

Microsoft is still using CR-LF to end lines, and that convention was used in your source file. The solution is to remove the CRs from the source file. google can tell you many ways to do this. Me, I'd just fire up emacs and remove them.

The driver kit in this example is for download on :

http://www.promise.com/support/download/

Ask your vendor for linux source code. The above isn't it.

How in earth could the Free Software Foundation and the GCC Team allowed this to happen?

Because we don't have the resource to nuke Microsoft off the planet yet... :-)

The gcc list isn't for trivial porting issue like this...

References:
- C Code mutilation by using gcc-3.3.x
  - From: Robert M. Stockmann

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