Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Thu, 15 Feb 2001 18:21:08 +0100 (MET) From: Jean Delvare To: "Larry Hall (RFK Partners, Inc)" Cc: cygwin AT sources DOT redhat DOT com Subject: Re: file descriptors opened as text files In-Reply-To: <4.3.1.2.20010215104635.017d17d8@pop.ma.ultranet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII > Its not a Cygwin invention. Its a MS one. Check out the documentation > for open()/_open() on the MSDN. They use the _O_BINARY flag. Don't get me > wrong. I hate text mode in all its forms. Perhaps Cygwin could've forgone > its use here. Maybe not. However, doing so here follows the MS lead and > wasn't a Cygwin concoction. I don't use MS development softwares. That's not the point here. Cygwin intends to provide an environment for fast port from Unix to Windows, so what it must look and behave like is Unix, not Windows. And the fast if, O_BINARY and O_TEXT are not defined on Unix systems. Moreover, a file descriptor is always working in binary mode on Unix. Thus, the choice Cygwin made here will necessary cause problems to anyone porting a software using file descriptors, and there must (and will) be thousands, for sure. I strongly believe that the correct behavior would be to consider any file descriptor as binary. People needing higher lever control are supposed to use handles anyway, not descriptors. -- /~~ Jean "Khali" Delvare -----\_ mail: delvare AT ensicaen DOT ismra DOT fr --------\ http://www.ensicaen.ismra.fr/~delvare/ ---=ISMRA/- ____________________________________________________ -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple