Mail Archives: djgpp/1999/12/21/12:08:34
> >> 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?
GCC does not recognise CR-only as a line end. This can be the cause
of some obscure errors:
#include <iostream> // rest of source file won't be read!
Another thing to watch out for is make, the *nix version only accepts
NL line ends and will give some cryptic error messages if it
encounters a CR.
- Raw text -