Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Message-ID: <36CB35C9.86D45693@cityweb.de>
Date: Wed, 17 Feb 1999 22:34:01 +0100
From: Corinna Vinschen <corinna DOT vinschen AT cityweb DOT de>
MIME-Version: 1.0
To: Paul Sokolovsky <paul-ml AT is DOT lg DOT ua>, DJ Delorie <dj AT delorie DOT com>,
        cygwin AT sourceware DOT cygnus DOT com
Subject: Re: Cygwin B20 - fseek under gcc fails to reposition on text files
References: <36CA92B5 DOT 844635AA AT cityweb DOT de> <17817 DOT 990217 AT is DOT lg DOT ua>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Paul Sokolovsky wrote:
>     So, for more than twenty years MS maintains myth about "special
> format" of text files of their systems. It's hardly believable. Since
> my old XT I quite nicely handled any text files - be they Unix \xa,
> Mac \xd, or "dos" \xd\xa . So there's nothing special to talk about
> "special" format of text files. Most tools available handled any type,
> and conversion between formats was quite feasible. With win32, such
> problems are ceased at all - I don't have no line endings problems, no
> encoding problems, even that unicode seams to be here.

As a matter of fact: Peter's c example, which opens this thread, does
not work with VC++, if the newline is not \r\n. Look into the source
of M$-ftell(), it can't work.

The best way would be to throw away and ignore any newline with
more than one single character.

But let's get serious.

IMHO, above all text file processing should be done according to the
underlying OS and it's vendor, also if this is wretched.

The second choice has the advantage, to be easy to implement.

The third choice should be implemented, if s.o. has nothing important
to do.

Regards,
Corinna


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