From: "Damian Yerrick" <NOSP AT Msnews@pineight.8m.com>
Newsgroups: comp.os.msdos.djgpp
References: <199912211215 DOT NAA25876 AT acp3bf DOT physik DOT rwth-aachen DOT de>
Subject: Re: parse error
Lines: 51
Organization: Pin Eight Software <http://pineight.8m.com/>
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Message-ID: <OQP74.1173$PK3.12128@dfiatx1-snr1.gtei.net>
X-Trace: +4MVL/a3L7NkZlWAfG+VXZtFn9R9OhRVsHXvMG+WbU/w6602I4iEEsxovVECPHEdZU0rk+OGzE7C!TEYG9zBQVY5hbkmfoLorr4zTdGtA6grG3+61eVswWAwJuJLGOWqDqkitiny9MtoyMXdFlSk=
X-Complaints-To: abuse AT gte DOT net
X-Abuse-Info: Please be sure to forward a copy of ALL headers
X-Abuse-Info: Otherwise we will be unable to process your complaint properly
NNTP-Posting-Date: Tue, 21 Dec 1999 18:40:46 GMT
Distribution: world
Date: Tue, 21 Dec 1999 18:40:46 GMT
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

"Hans-Bernhard Broeker" <broeker AT physik DOT rwth-aachen DOT de> wrote:
> You wrote:
>
> > 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!
>
> CR-only is a rare thing to come across. It's what you get in Apple
> Macintosh text files. But Mac users usually know they have
> to transfer text files as text, not binary, to other architectures

But drag-and-drop copying of a text file to (say) a
FAT volume will copy the file as binary.

> The fact that Macs store a 'file type' with each file, in their
> 'resource fork' probably helps to avoid this type of bug.

Actually, the "file type" is a four-character string stored in
the directory. It's stored next to another four-character
string called "creator", which stores the ID of the program
that created the file.

The "resource fork" is a file stored alongside the real file.
It generally contains similar things to what is at the end of
a Windows program file (icons, pictures, etc.)

But this is swinging off-topic for a DOS programming NG.

> OTOH, you'll most probably see right away that something's
> wrong with such files, in any DOS or Windows editor, as
> soon as you open it.

For example, in DOS Edit, you see eighth notes instead of returns.

--
Damian Yerrick    http://yerricde.tripod.com/
View full .sig:  http://www.rose-hulman.edu/~yerricde/sig.html










and now you must pay...