Message-Id: <5.0.2.1.0.20001209125228.025cbec0@pop5.banet.net>
X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Sat, 09 Dec 2000 12:59:52 -0500
To: djgpp-workers AT delorie DOT com
From: "Peter J. Farley III" <pjfarley AT banet DOT net>
Subject: Why are we using offset_t and not off64_t?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Reply-To: djgpp-workers AT delorie DOT com

I'm finally getting around to putting in the FAT32 support to the new 
fcntl, and in looking up all the types and definitions needed, I see 
that for "long long int" offsets we are using "offset_t" instead of 
"off64_t", such as is used in glibc-2.1.3.  Can anyone enlighten me why 
we are doing this?  Why not just lift the __USE_LARGEFILE64 and 
__USE_FILE_OFFSET64 code from glibc's posix/sys/types.h, suitably 
modified for DJGPP?

TIA for any info you can provide.

---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
                      pjfarley AT banet DOT net)