Re: fseek() vs. fseeko()

[Ralf Corsepius <ralf dot corsepius at rtems dot org>]

On 06/20/2012 03:52 PM, Sebastian Huber wrote:
> On 06/20/2012 03:41 PM, Joel Sherrill wrote:
> > On 06/19/2012 09:42 AM, Sebastian Huber wrote:
> > > On 06/19/2012 04:08 PM, Corinna Vinschen wrote:
> > > > Along these lines, fgetpos and fsetpos are a bit tricky since they
> > > > depend on the definition of fpos_t in include/stdio.h. Right now,
> > > > only Cygwin defines fpos_t as 64 bit type in stdio.h, all other
> > > > targets define fpos_t as 32 bit and fpos64_t as 64 bit type to make
> > > > a clear distinction between the 32 bit and the 64 bit set of functions.
> > Speaking for myself, I would like the methods to default to all 64-bit
> > versions on RTEMS (when the CPU defaults to 64-bit).
>
> I would prefer the FreeBSD approach. I fixes also some EOVERFLOW problems.

An apparently minor problem, otherwise this issue already would have had 
an visible impact throughout the decades the newlib code is in place :-)

> http://svnweb.freebsd.org/base/head/lib/libc/stdio/fseek.c?revision=178287&view=markup

I not opposed to this, except that, in general FreeBSD code (unlike 
newlib) has not seen any exposure to 8/16 bit targets.

Ralf