1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
Q: Is PRCS Y2K complaint?
(Short answer: yes)
Just about everything date or time related in PRCS depends upon RCS.
RCS and PRCS communicate using date strings which are expressed in
UTC such as "1999/02/24 00:36:15". Earlier versions of RCS used
a 2-digit date field, but this has been fixed for some time (see below).
Paul Eggert is the maintainer of RCS, and he wrote the majority of the
code used in PRCS for date-string-to-time conversion. This code is located
in the files src/maketime.c, src/partime.c, src/include/partime.h, and
src/include/maketime.h. These can be found in, for example, the diffutils
release, which Paul Eggert also maintains. So, PRCS is as Y2K complaint
as the underlying RCS installation, which is already required to be
RCS-5.7 (use `prcs config' to determine whether this is propertly set
up). Paul has also proof-read the small amount of code written by myself
to format RFC-822 date strings and recommended the use of an ISO-9600
encoding in future versions. PRCS-2.x uses the newer date string
standard, stores dates internally using arbitrary precision integers,
and has nanosecond precision.
Paul Eggert <eggert@twinsun.com> adds, concerning RCS:
RCS's Y2k bugs were fixed a long time ago, in time for RCS 5.5
(dated 1990), so unless you are using a very old version of RCS
you shouldn't have a problem. Since 1990 there has been only
one valid bug report about Y2k-related issues in RCS. This report
was not actually about a bug in RCS itself; it was about an
incompatibility with MKS RCS, as MKS had installed an incompatible
fix to the Y2k problem in their own version of RCS. This problem
was fixed by extending RCS to parse the incompatible MKS syntax in
RCS files; this fix appears in RCS 5.7 (dated 1995).
|
