Newsgroups:	comp.os.msdos.djgpp
From:	manni DOT heumann AT gmx DOT de (Manni Heumann)
Subject:	Re: parse error
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 991220103732 DOT 6937A-100000 AT is>
X-Newsreader:	News Xpress 2.01
Date:	Mon, 20 Dec 1999 10:31:17 GMT
NNTP-Posting-Host:	dhcp33-114.uni-bielefeld.de
Message-ID:	<385e057b@news.uni-bielefeld.de>
X-Trace:	20 Dec 1999 11:31:23 +0200, dhcp33-114.uni-bielefeld.de
Lines:	24
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <Pine DOT SUN DOT 3 DOT 91 DOT 991220103732 DOT 6937A-100000 AT is>, djgpp AT delorie DOT com wrote:
>
>On Mon, 20 Dec 1999, Jude T. DaShiell wrote:
>
>> I think a parse error can happen if line endings aren't correct.  Say a
>> piece of code compiled and working on Unix systems is compiled with djgpp.
>
>Not true: DJGPP has no problems with Unix-style line endings.  All the 
>sources of GNU packages ported to DJGPP have Unix-style line endings, and 
>I have never needed to run them through utod.
>
>As a matter of fact, beginning with GCC 2.91 (I think), the Unix version 
>of the compiler can compile sources with DOS-style line endings as well.

A few weeks ago somebody asked for assistance with his parse errors. And it 
turned out that he had strange characters (from a Dos /Win view) at the end of 
his lines. I don't know whether these were unix-style and I don't remember 
what the actual character was, but they surely were the source of his parse 
errors. Does anybody remember?


--

Manni

- Raw text -