From: eplmst AT lu DOT erisoft DOT se (Martin Stromberg)
Message-Id: <199902031453.PAA19941@juno.erisoft.se>
Subject: Re: _llseeks()'s return value
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Wed, 3 Feb 1999 15:53:53 +0100 (MET)
Cc: djgpp-workers AT delorie DOT com (DJGPP-WORKERS)
In-Reply-To: <Pine.SUN.3.91.990203162923.11389E-100000@is> from "Eli Zaretskii" at Feb 3, 99 04:32:59 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

> 
> 
> On Wed, 3 Feb 1999, Martin Stromberg wrote:
> 
> > Ok. But this means _llseek() will have to reposition the pointer to
> > the beginning or the end of file and seek from there. And seeking from
> > current position won't work. Or am I missing something?
> 
> Seeking from current position *will* work, but the return value won't be 
> correct when the resultant position is beyond 2GB.  This is DOS bug, 
> so just document it and continue.

Oh, I was just thinking that instead of returning a bogus value, we
should return fail as I thought one important use of seek from the
current position zero steps was having it return the current
postition. (Hence, not support seeking from current postion at all.) 

But if nobody says otherwise, I'll do it the Eli way.

Somebody doesn't happen to know some interrupt for seeking that
returns valid data on file positions bigger than 2^31?

> As for repositioning, when seeking is relative to beginning or end, you 
> need to do that anyway, no?  Or did *I* miss something?

Ehum... No.


Right,

							MartinS