On Mon, Apr 12, 2010 at 01:19:07PM +0200, Corinna Vinschen wrote: >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.
That sounds good but I don't really see what this has to do with the cygwin-doc package. That is the consumer of these types of changes, not the driver. cgf -- 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
