On Sun, Aug 06, 2000 at 11:07:02AM -0700, Russ Allbery wrote: > Basically, you don't want to go anywhere near this mess; it eats people. I agree. > I see two reasonable options to go with instead. One is to just use a > binary flag that says use UTC or not; this is the simplest and most > reliable to explain. The other is to allow a timezone offset; this > doesn't deal with daylight savings time and historic time zone changes, > but it provides enough power for most of what people want to do and if you > want to deal with the rest you have to deal with time zone naming. This makes an incredible amount of sense. We could even let the user specify a coderef to a sub that implements their own particular timezone oddities. (i.e. a sub to tell date() what the TZ offset is) -Scott -- Jonathan Scott Duff [EMAIL PROTECTED]
- Re: RFC 48 (v1) Replace localtim... Glenn Linderman
- Re: RFC 48 (v1) Replace localtime() and gmtime() ... Nathan Wiger
- Re: RFC 48 (v1) Replace localtime() and gmtim... Jonathan Scott Duff
- Re: RFC 48 (v1) Replace localtime() and gmtim... Johan Vromans
- Re: RFC 48 (v1) Replace localtime() and g... Andy Dougherty
- Re: RFC 48 (v1) Replace localtime() and gmtim... Bart Lateur
- Re: RFC 48 (v1) Replace localtime() and gmtime() ... Gisle Aas
- Re: RFC 48 (v1) Replace localtime() and gmtim... Bryan C . Warnock
- Re: RFC 48 (v1) Replace localtime() and gmtim... Nathan Wiger
- Re: RFC 48 (v1) Replace localtime() and gmtime() with ... Russ Allbery
- AGAINST RFC 48 (v1) Replace localtime() and gmtim... Jonathan Scott Duff
- Re: RFC 48 (v1) Replace localtime() and gmtime() ... Jarkko Hietaniemi
- Re: RFC 48 (v1) Replace localtime() and gmtime() with ... Damian Conway
- Re: RFC 48 (v1) Replace localtime() and gmtime() ... Nathan Wiger
- Re: RFC 48 (v1) Replace localtime() and gmtime() ... Bart Lateur
- Re: RFC 48 (v1) Replace localtime() and gmtim... Nathan Wiger
- Re: RFC 48 (v1) Replace localtime() and gmtime() with ... John Tobey