From: Martin Str|mberg <ams AT ludd DOT luth DOT se>
Message-Id: <200301190925.h0J9PM923192@brother.ludd.luth.se>
Subject: Re: lseek() calling llseek()
To: djgpp-workers AT delorie DOT com
Date: Sun, 19 Jan 2003 10:25:22 +0100 (MET)
In-Reply-To: <Pine.SUN.3.91.1030119080546.7077C-100000@is> from "Eli Zaretskii" at Jan 19, 2003 08:08:32 AM
X-Mailer: ELM [version 2.5 PL2]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

According to Eli Zaretskii:
> On Sat, 18 Jan 2003 lnobody AT delorie DOT com wrote:
> > -A file lseek handler (@pxref{lseek}).
> > +A file lseek handler (@pxref{lseek}).  Here for backwards
> > +compatibility.  Use __FSEXT_llseek instead.  If you have a
> > +__FSEXT_llseek handler you don't need a __FSEXT_lseek handler as lseek
> > +calls llseek internally.
> 
> This is okay, but please put all the symbols, like `lseek' and 
> `__FSEXT_*', in @code.

You mean like this:
A file @code{lseek} handler (@pxref{lseek}).  Here for backwards
> > +compatibility.  Use @code{__FSEXT_llseek} instead.  ...

That means I'll change almost every line in that file, if I understand
you correctly, for that first @code is missing in many places.

> > +  llseek_offset = llseek(handle, offset, whence);
> 
> Is `llseek' defined to `_llseek' on stubs.h?

Yes, it's in stubs.h. 

>   If not, is it Posix? 

No (Linux man page says it Linux specific; it's dated 1995, though).


Right,

						MartinS