Date: Sun, 5 Aug 2001 10:09:59 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: djgpp AT delorie DOT com Subject: Re: ANNOUNCE: DJGPP port of GNU Sed 3.02.80 uploaded In-Reply-To: <9kiad7$r0q@moe.cc.utexas.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On 4 Aug 2001, Henry Churchyard wrote: > >> 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 I didn't say it did. But because you were nitpicking, so did I ;-) > 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" Which makes ^Z more ``a DOS feature'' than the CR-LF issue: ^Z is interpreted by device driver, which is conceptually a part of the OS.