After daylight savings time went into effect in my time zone
this weekend, the 'date' and 'time' functions have been
behaving strangely. Observed symptoms:
The first time 'date' is called after scsh start-up, it
returns a date object that causes the 'time' function to
return an incorrect result. However, on subsequent calls
'date' seems to return a correct value:
Scsh 0.4
> (time)
859893560
> (time (date))
-7201
> (time (date))
859893573
> (time (date))
859893575
> (exit)
However, the slots in the date object seem to contain
correct values:
Scsh 0.4
> (define now (date))
> (date:year now)
97
> (date:month now)
3
> (date:month-day now)
1
> (date:hour now)
13
> (date:minute now)
19
> (date:seconds now)
55
> (date:tz-name now)
"MET DST-2"
> (date:tz-secs now)
7200
> (date:summer? now)
#t
> (date:week-day now)
2
> (date:year-day now)
90
> (time now)
-7201
> (exit)
This has been observed under SunOS 4.3.1_U1 and, using the
same binary, under SunOS 5.5. This *might* be a SunOS
related thing and not a scsh bug, but I haven't been able to
provoke similar behaviour in non-scsh programs.
Leif Nixon SoftLab AB
-------------------------------------------------
E-mail: nixon@softlab.se Phone: +46 13 23 57 61
-------------------------------------------------
|