On Sun, May 06, 2001 at 08:41:49AM +0530, Abhijit Menon-Sen wrote:
> On 2001-05-05 21:19:26, [EMAIL PROTECTED] wrote:
> >
> > Do we want the internal representation to be a string?
>
> It's probably easiest.
>
> > [struct GDate] fits nicely inside 64 bits so you can store it as a
> > number in databases and such. Maybe we can use something like this but
> > with time info included [...]
>
> If you include time info, it no longer fits into 64 bits. Given that the
> average case for the format I proposed is 128 bits[*], it's probably not
> worth the hassle of an explicit byte ordering and a fixed-length data
> structure to use a non-ASCII representation.
Hmm? second-precision TAI is 64 bits, nanosecond is 64+32 and attosecond
precision is 64+32+32. how is this ever going to average to 128? So at
least for second-precision times, using a 64bit integer still makes sense.
In any case, I think building our base date/time module around libtai
would be a good idea.
Martijn
