[EMAIL PROTECTED] (Jonathan Scott Duff) wrote on 15.08.00 in <[EMAIL PROTECTED]>: > You're right, there should be just one date/time routine. But it is > *extremely* difficult to incorporate time zones in a portable fashion. > They change at legislative whim. But if utcdate() (or whatever we > call it) had a way to specify an offset from UTC, that would be just > fine. There's a reason why the Olson timezone routines&data exist. Use them. Make the data easily updatable (actually, it would be hard to make it *not* easily updatable). Problem solved. MfG Kai
- Re: RFC 48 (v2) Replace localtime() and g... iain truskett
- Re: RFC 48 (v2) Replace localtime() and gmtim... Bryan C . Warnock
- Re: RFC 48 (v2) Replace localtime() and g... Nathan Wiger
- Re: RFC 48 (v2) Replace localtime() and gmtime() with ... Jonathan Leffler
- Re: RFC 48 (v2) Replace localtime() and gmtime() with ... Tim Jenness
- Re: RFC 48 (v2) Replace localtime() and gmtime() ... Nathan Wiger
- Re: RFC 48 (v2) Replace localtime() and gmtim... Tim Jenness
- Re: RFC 48 (v2) Replace localtime() and gmtim... Philip Newton
- Re: RFC 48 (v2) Replace localtime() and gmtime() with ... Bart Lateur
- Re: RFC 48 (v2) Replace localtime() and gmtime() ... Jonathan Scott Duff
- Kai Henningsen