This is the mail archive of the newlib@sourceware.org mailing list for the newlib project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: fseek() vs. fseeko()


On Jun 20 08:10, Eric Blake wrote:
> On 06/20/2012 07:41 AM, Joel Sherrill wrote:
> 
> > It might be better to switch to explicit selection like
> > 
> > if "CPUs we know we want 64 bit"
> 
> I think there are situations where you want to default off_t to 64-bit
> even on CPUs that only support 32-bit (think Cygwin, for instance).  I
> think a better hierarchy is:
> 
> Use 64-bit off_t if large files are reasonable, regardless of CPU size
> else use 64-bit off_t if long if 64-bit
> else use 32-bit off_t

Sounds reasonable.  Actually, isn't the __LARGE64_FILES definition already
a good indicator whether 64 bit off_t and fpos_t are feasible?


Corinna

-- 
Corinna Vinschen
Cygwin Project Co-Leader
Red Hat


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]