There is an absolute standard for this -- the timezone that's in an internet-style (date and) time string says that earlier times are a negative offset from GMT. (For example, the U.S. has a negative offset from GMT.)
I think you did it backwards. It must match the internet time standard -- when there are only two choices, our "some standard" should be the one that has already been chosen by the world. J. Merrill Senior Software Engineer 3M Health Information Systems, Inc. Michael Pliskin <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 07/14/2008 12:02 PM Please respond to Michael Pliskin <[EMAIL PROTECTED]>; Please respond to Neko intermediate language mailing list <[email protected]> To Neko intermediate language mailing list <[email protected]> cc Subject Re: [Neko] API for local/GMT time conversion Hello Nicolas, MP> Hmm then we're reducing the solution to just get_tz_offset function - MP> minutes seem non-standard for me, maybe seconds is better. Ok, will MP> make it and send a patch soon. ok, here is a simple patch. Note that I am subtracting local from GMT, so GMT+2 will have negative offset. Not sure if it is the best but we just need to stick to some convention. -- Best regards, Michael mailto:[EMAIL PROTECTED] "date.c.patch" deleted by J. Merrill/HI-HealthInfo/3M/US] -- Neko : One VM to run them all (http://nekovm.org)
-- Neko : One VM to run them all (http://nekovm.org)
