diff --git a/Docs/xacc-main.html b/Docs/xacc-main.html index 7676a891c7..3193bb5d2b 100644 --- a/Docs/xacc-main.html +++ b/Docs/xacc-main.html @@ -27,6 +27,7 @@
  • Reports
  • Using Double Entry
  • Using Income/Expense Accounts +
  • Y2K Considerations
    diff --git a/Docs/xacc-y2k.html b/Docs/xacc-y2k.html new file mode 100644 index 0000000000..407335f2d4 --- /dev/null +++ b/Docs/xacc-y2k.html @@ -0,0 +1,31 @@ + + + + GnuCash Y2K Readiness + + + +

    GnuCash Y2K Readiness

    + Gnucash version 1.1.25 and later store all dates as seconds and + nanoseconds, where the seconds are stored in a 64-bit signed integer. + This should suffice to store dates in the distant past as well as the + distant future, as long as they are less than several dozen times the + age of the universe. +

    + The file format for version 1.1.25 and later stores dates in the + above-described fashion. +

    + Some internal routines use the time_t type to express + seconds. Note that on most OS'es, this is a 32-bit quantity, and + is limited to the Unix era (Jan 1970 to August 2038). We beleive + that a signed int (31-bits) is never used internally to represent time. + Note that 31-bit quantities experience a crisis in April 2004. + We beleive that GnuCash will survive the 2004 crisis. +

    + Backup and log files are time-stamped using the standard Unix + ctime() routine, which takes a time_t argument. + Thus, the backup and log mechanism may experience trouble in 2038. + + + +