Mail Archives: djgpp/2001/08/04/22:30:12
In article <7458-Sat04Aug2001103737+0300-eliz AT is DOT elta DOT co DOT il>,
Eli Zaretskii <djgpp AT delorie DOT com> wrote:
>> From: "Henry Churchyard" <churchh AT crossmyt DOT com>
>>> on platforms, like DOS/WIN95, that distinguish between
>>> text and binary files. This will allow to process files that
>>> contain embedded ^Z and lone ^M characters.
>> DOS doesn't make any distinction whatsoever between binary and text
>> files at the file-system level. [...CR vs. CR-LF problem] is
>> caused by peculiarities of Unix/C, not peculiarities of DOS.
> That's true, except that the special meaning of ^Z doesn't come from
> the Unix text notion, but rather from CP/M.
Yes, but ^Z actually also has no special status as far as the basic
DOS filesystem or file open/read/write function calls (such as INT 21H
AH=3DH, AH=3FH etc.) go -- pretty much the only places where the DOS
operating system itself really treats ^Z specially are in some cases
to mark the end of an input stream when reading in directly from a
"character device" (not a disk file), and in the non-binary
file-concatenation form of the COPY command as implemented by the
COMMAND.COM interpreter.
--%!PS
10 10 scale/M{rmoveto}def/R{rlineto}def 12 45 moveto 0 5 R 4 -1 M 5.5 0 R
currentpoint 3 sub 3 90 0 arcn 0 -6 R 7.54 10.28 M 2.7067 -9.28 R -5.6333
2 setlinewidth 0 R 9.8867 8 M 7 0 R 0 -9 R -6 4 M 0 -4 R stroke showpage
% Henry Churchyard churchh AT crossmyt DOT com http://www.crossmyt.com/hc/
- Raw text -