On Tue, 6 Mar 2007, Anthony R. J. Ball wrote:
It might make sense in that case to return the observance date and somehow return the change that happens, or add another call that returns that data for that change. Maybe return a datetime object and a duration object? Or have a separate call that returns a duration.
Internally, there are objects that actually represent the nature of a given observance (start datetime, offset from UTC, is it dst, etc). They're pretty horrid, and tied tightly to the Olson DB representation of a time zone, so I wouldn't want to encourage people to use them as-is.
However, something with some of the same info seems like a natural thing to return from these methods.
-dave /*=================================================== VegGuide.Org www.BookIRead.com Your guide to all that's veg. My book blog ===================================================*/
