Re: Enhancement Topics (Format and Usage Bugs)

dk wrote:
> Actually...
>
> On most systems, time_32t is a signed 32-bit integer with a max. of 03:14:07
> UTC on Tuesday, January 19, 2038, and only if made "unsigned" does it go on
> to 2106.
>
> time_64t on most systems is a signed 64-bit integer.  If treated as
> "unsigned", it would have a max. on December 4, 292,277,026,596.
>
> I doubt very much that I (or PasswordSafe) will be here for the second date
> (290+ billion years time) and I think it is unlikely that I will really care
> about it on the first!
>
> David
>
>
>   

Are you saying that you are developing Password Safe for your own 
purposes? - Indeed in this case these considerations are irrelevant, but 
also your contradiction is!

Allowing a 64-bit value as *alternative* does not cause problems but 
brings benefits, so why not admit it? - It does not cost more storage 
and all readers who are not interested in 8 bytes have to do is just 
read the first 4 bytes, which they probably are doing already anyway.

- Wolfgang




-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/