Mail Archives: djgpp/2001/02/16/18:22:57
Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de> wrote:
> I now believe that the problems I thought I remembered were actually
> the other way round: *Linux* GCC used to have all kinds of problems
> with DOS sources brought back to the Linux platform. And the main
> problem really was preprocessor line continuation, then: "\\\r\n" in
> the source was not seen by the preprocessor as a valid "backslash
> followed immediately by line end" sequence, which broke multiline
> macro definitions ---
Another, IIRC, was with C++ style comments causing the remainder of
the file to be lost: #include "my_lib.h" // Prototypes for my lib.
> the error messages you get from that are quite
> "interesting", and almost completely unhelpful.
This seems the norm, `make' used to emit an obscure error message too.
Presumably if the author would account for dos style EOL, then they
may as well handle it rather than introduce another error message.
Another one that had me stumped for a while the other day was BASH
v2.03. Native unix version simply refuses to run any script with CRLF
line ends, again the error message is most unhelpful.
Both gcc and make are fixed now - would this be due to back porting of
changes from DJGPP?
- Raw text -