This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Updated: cygwin-doc-1.7-1
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 12 Apr 2010 13:19:07 +0200
- Subject: Re: Updated: cygwin-doc-1.7-1
- References: <4bc25bad.071abc0a.2742.ffff92f4SMTPIN_ADDED@mx.google.com> <o2r6910a61004120156y7b7167ecua91f23e20afa21f2@mail.gmail.com>
- Reply-to: cygwin at cygwin dot com
On Apr 12 10:56, Reini Urban wrote:
> 2010/4/12 Christopher Faylor:
> > I have just uploaded a long-overdue update to the Cygwin documentation
> > package. ?This package provides man and info pages for cygwin utilities
> > and *some* of the Cygwin api. ?It reflects the current state of Cygwin
> > and newlib as of this date.
>
> http://cygwin.com/cygwin-api/std-notes.html
> "lseek only works properly on binary files."
>
> Shouldn't that say:
> "lseek only works properly on files mounted or opened binary, and not
> in textmode."
>
> textfiles mounted or opened binary do work fine IMHO.
I see what you mean but I don't quite understand your last sentence.
Do you mean this?
mounted binary, opened modeless -> lseek works fine
mounted binary, opened binary -> lseek works fine
mounted binary, opened text -> lseek is unreliable
mounted text , opened modeless -> lseek is unreliable
mounted text , opened binary -> lseek works fine
mounted text , opened text -> lseek is unreliable
That's what we're trying to say. So I changed this locally to
<para><function>lseek</function> only works properly on files opened in
binary mode. On files opened in textmode (via mount mode or explicit
open flag) its positioning is potentially unreliable.</para>
Does that sound ok? If so, I check it in.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple