[
Lists Home |
Date Index |
Thread Index
]
Rick Jelliffe wrote:
>
> Sure, lets make XML unsuitable for use in UNIX pipes by allowing ^D.
> And for Perl and Python text-processing programs that use standard in and
> expect EOF (^D or ^Z).
On Unix, ^D is only interpreted as an end-of-file signal
when it's typed at a terminal, not when it's stored in a file
or transmitted over a socket or pipe. Similarly for
^C, ^Z, ^\, ^S, ^Q, and other control characters; these have
no special meaning as far as the file system or stdio
are concerned.
CP/M and MS-DOS on the other hand *do* interpret ^Z as an EOF
character in text files. CP/M doesn't keep track of file sizes
in bytes, only the number of blocks, so it needs an in-band EOF
indicator. Some MS-DOS utilities inherited this convention from
CP/M (TYPE, EDLIN.COM) but Windows seems to have abandoned it;
EDIT.COM, NOTEPAD.EXE, and WORDPAD.EXE all have no trouble editing
text files with ^Z's in them.
--Joe English
jenglish@flightlab.com
|
