Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <c=DK%a=_%p=CD-Danmark%l=CDDKSERVER-990621150319Z-15482@cddkserver.cddk.dk>
From: Peter Ring <PRI AT cddk DOT dk>
To: "'earnie_boyd AT yahoo DOT com'" <earnie_boyd AT yahoo DOT com>,
        "'cygwin users'"
	 <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE: LF vs. CR/LF (WAS: Problems with libtiff!)
Date: Mon, 21 Jun 1999 17:03:19 +0200
X-Mailer:  Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

What is the correct way to open, read, and write a 'text' file on a
filesystem shared between a number of different operating systems?
(please note that this is in effect what cygwin amounts to).

The scenario could be a 'text' file shared between MacOS, WinNT, and
some UNIX-like OS. The file might be shared in several ways, some of
which would make it impractical (if not outright nonsense) to talk about
one specific OS 'hosting' the file.

Some applications, e.g. emacs, try to guess from the file's content what
to do. Obviously, this works only for interactive applications.

I won't argue with the benefits of explicitly opening files 'rb'. I just
wonder why anyone would ever want to do anytning else?

Kind regards
Peter Ring


-----Original Message-----
From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com]
Sent: Monday, June 21, 1999 4:29 PM
To: cygwin users
Subject: Re: LF vs. CR/LF (WAS: Problems with libtiff!)


<snip>

Welcome to the world of portable programming.

<snip>

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com