Darren Reed wrote: > FWIW, I think we're approaching the time when we are going to need to > start thinking about transitioning time_t to being uint64_t - even for > 32bit platforms (as a point of interest, earlier this year we went past > the point in time where a 32bit time_t can hold the start and end dates > of a 30 year mortgage.)
No banking software I've been exposed to uses unix/C types for this kind of thing. (That would be easier and very much less error prone than what they do actually use;-) > Currently we have it as 'long' (in <sys/types.h>), so we get 32bit > or 64bit depending on the CPU architecture. > > The fallout of that should be things like stat64(2), etc... stat64(2) already exists -- you get it with largefile compiles. However, I don't think the time fields are 64 bit. -- Andrew
