On 21/10/2011 12:33 AM, Henning Brauer wrote: > * Janne Johansson <icepic...@gmail.com> [2011-10-20 15:11]: >> What I meant was as you say, we can change the include file to say "use 64 >> bits for time" and recompile some apps, but if the database file format or >> the over-the-wire formats don't support 64 bits for specifying time, you'd >> be screwed anyway. That's why applications, formats and protocols need to >> change, since many of them use 32 bits today. > > anything clean just uses time_t and is thus fixed by recompiling. > > now, reality check, there is way too much crap out there that makes > dumb assumptions. but "many of them use 32 bits today" makes it sound > like a) that was common and b) right. it isn't. certainly not b). time > will tell us (oh the irony) about a). >
I was hoping to hear if there was a plan or if someone was working on moving to 64 bit time_t, I have been digging around in the source code of -current recompiling the kernel with arch amd64 _types.h time_t typedef'd as __int64_t but am now tracing where else it is defined and other compilation errors, is what I am trying to do madness and there is a known thing that won't be changed? That is to say, am I wasting my time (ha)?
