Re: timezones & date() breakage

On Wed, 28 Sep 2005, Steph wrote: > > > I wouldn't call it broken, just less inituitive. But besides that point, > > I looked at some data and have a patch that allows the timezone guessing > > code to also check against the GMT offset, and not only the > > abbreviation. This means that with these DB entries: > > > > { "idt", 1, -HOUR ( 3), "Asia/Tel_Aviv" }, > > { "idt", 1, -HOUR (4.5), "Iran/Teheran" }, > > { "idt", 1, -HOUR (6.5), "Asia/Calcutta" }, > > > > IDT will be recognised correctly for all three variations. > > Cool, you can generate a sane E_STRICT from that too (telling people what > they need in their php.ini to speed things up). It already does that: Strict standards: date(): It is not safe to rely on the systems timezone settings, please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. We use 'Europe/Berlin' for 'CEST/2.0' instead. in Command line code on line 1 regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org