This is the mail archive of the
newlib@sourceware.org
mailing list for the newlib project.
Re: fseek() vs. fseeko()
On 6/19/2012 1:11 PM, Corinna Vinschen wrote:
On Jun 19 18:27, Ralf Corsepius wrote:
Ok, then this is a bug in the RTEMS targets using 64-bit off_t.
No. This is a bug in newlib.
fseeko etc. are supposed to take abstract types "off_t".
RTEMS relies upon this assumption, but obviously can't handle this.
Since> the fseeko64() etc. are non-standard this should be
invisible for the> user.
Agreed. They should not be used anywhere and be removed from newlib.
That's obviously not possible for backward compatibility.
Corinna
This makes me wonder about non-standard creep. Is there anything written
with fseeko, fseeko8, fseeko16, fseeko32, fseeko64 or fseeko128 that
could not be poosibly written with an appropriate fgetpos and fsetpos
(the standard functions that deal with off_t)? Are those two functions
substandard for what one tries to do?
Gregory