Mon, 23 Jun 2003 07:38:00 -0400
On Monday 23 June 2003 05:35, Simon Marlow wrote:
> you can't accurately use
> addSeconds or addPicoseconds on a CalendarTime in the future without
> knowing where leap seconds occur. This is an interesting bug/feature
> that I just realised.
Similarly, converting between ClockTime and CalendarTime in time zones with
daylight savings is somewhat unpredictable. In my time zone, the
determination of when to set clocks ahead has changed a couple of times in
the past 20 years.
I wouldn't want the API made more complex in order to accomodate these