On Mon, 2 Dec 2002, Steffen Kaiser wrote: > However, the POSIX.1 rationale includes statements like this: > "The C Standard [aka ANSI-C] includes functions fgetpos() and fsetpos(), > which work on very large files by use of a special positioning type." > -and- > "An invalid file offset [...] may be both implementation defined and > device dependent [...]. A negative file offset may be valid for some > devices in some implementations." > -and- > "See B.6.5.2 for a explanation of the use of signed and unsigned offsets > with lseek()." But I can't find any references in there. > > So, to deal with files beyond 2GB from within C is an "implementor > defined" issue. > > The API function DOS-42 is a straight forward implementation of this > definition with sizeof(off_t) == 4.
it's a little different from lseek(2). The difference is in the return value. POSIX: error: (off_t)-1 returned and errno set DOS: error: CF set and error in AX. This makes it possible for DOS-42 to use unsigned off_t's with wrap-around semantics. Bart ---------- list options/archives/etc.: http://www.topica.com/lists/fd-dev unsubscribe: send blank email to: [EMAIL PROTECTED] ==^================================================================ This email was sent to: archive@mail-archive.com EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rv5.bbRv4l.YXJjaGl2 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
