Dear Stephen,
You're correct in assuming that (current-time-string) gives the correct result
always. However, i've never seen this behaviour with the native windows port of
XEmacs, only with the cygwin version.... so why does only the windows version
do-the-right-thing?
Jaap-Henk
On Fri, 5 Jul 2002 05:01:36 +0200 "Stephen J. Turnbull"
<stephen(a)xemacs.org> writes:
>>>>> "Jaap-Henk" == Jaap-Henk Hoepman
<hoepman(a)cs.utwente.nl> writes:
Jaap-Henk> After a suspend and the next resume, the value of
Jaap-Henk> (decode-time (current-time)) has increased by more than
Jaap-Henk> a day (see eg header of this mail; that's how i
Jaap-Henk> discovered this in the first place)! This happens
Jaap-Henk> independent of the length of the suspended state,
Jaap-Henk> although it seems that the longer the system is
Jaap-Henk> suspended, the larger the time increase
Jaap-Henk> becomes. Needless to say both windows and cygwin report
Jaap-Henk> the correct time.
This is a Windows or BIOS bug; correct time after resume depends on
what library API you use. There's another function,
current-time-string IIRC, that gives correct results. Presumably one
looks at system time, the other at the hardware clock.
I don't know why XEmacs uses different library calls in different
places, and until I do I'm not going to make the "obvious" change,
since this is Windows breakage.
--
Jaap-Henk Hoepman | Come sail your ships around me
Dept. of Computer Science | And burn your bridges down
University of Twente | Nick Cave - "Ship Song"
Email: hoepman(a)cs.utwente.nl === WWW:
www.cs.utwente.nl/~hoepman
Phone: +31 53 4893795 === Secr: +31 53 4893770 === Fax: +31 53 4894590
PGP ID: 0xF52E26DD Fingerprint: 1AED DDEB C7F1 DBB3 0556 4732 4217 ABEF