Re: Enhancement Topics (Format and Usage Bugs)

Looks good to me.

I have one point with the *time_t* format. - FYI, the 32-bit integer 
value has a final date of  2106-02-07 07:28:15 CEST. People, this is 
less than 100 years from now! :) - I'ld strongly suggest to declare the 
64-bit value as a valid alternative for time_t. Note that this does not 
conflict existing 32-bit values in little endian orientation. Readers 
just may detect the length of a value; also readers who only read the 
first 4 bytes still gain the correct values (until 2106).

- Wolfgang


ronys wrote:
> Hi folks,
>
> Good discussion. I agree that the format description is one of the more
> important parts of the project (probably what will outlive the application
> itself, not to mention myself).
>
> I've updated the document a bit, adding an explicit 'representation' section
> 3.1:
> http://passwordsafe.svn.sourceforge.net/viewvc/passwordsafe/trunk/pwsafe/pws
> afe/docs/formatV3.txt?view=markup
>
> Constructive comments, as usual, are welcome. Other comments > /dev/null.
>
> 	Cheers,
>
> 		Rony
>
>
> -------------------------------------------------------------------------
> 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/
> _______________________________________________
> Passwordsafe-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/passwordsafe-devel
>
>   

-------------------------------------------------------------------------
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/