IntenseFinance/gnucash
3
0
Fork 0
mirror of https://github.com/Gnucash/gnucash.git synced 2025-02-25 18:55:30 -06:00
Code Issues Packages Projects Releases Wiki Activity

y2k stuff

Browse Source 
git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@1457 57a11ea4-9604-0410-9ed3-97b8803252fd
This commit is contained in:
Linas Vepstas
1998-12-20 09:12:57 +00:00
parent a59c475b6b
commit cdc5993634
2 changed files with 32 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
Docs/xacc-main.html
View File

@@ -27,6 +27,7 @@
<li><a href="xacc-reports.html">Reports</a>
<li><a href="xacc-double.html">Using Double Entry</a>
<li><a href="xacc-expense.html">Using Income/Expense Accounts</a>
<li><a href="xacc-y2k.html">Y2K Considerations</a>
</ul>
<hr>

31
Docs/xacc-y2k.html Normal file
View File

@@ -0,0 +1,31 @@
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<html>
<head>
<title>GnuCash Y2K Readiness</title>
</head>
<body bgcolor="#eeeeee">
<h1>GnuCash Y2K Readiness</h1>
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.
<p>
The file format for version 1.1.25 and later stores dates in the
above-described fashion.
<p>
Some internal routines use the <tt>time_t</tt> 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.
<p>
Backup and log files are time-stamped using the standard Unix
<tt>ctime()</tt> routine, which takes a <tt>time_t</tt> argument.
Thus, the backup and log mechanism may experience trouble in 2038.
</body>
</html>