Pierre Joye wrote:
And I stop here for this discussion, I do not see any new arguments on both sides and a default TZ will very unlikely happen. Packagers could deal with that easily and application developers as well.
Isn't the point here that this only became a problem when the NEED for a default time zone was forced on us? What I should be saying is not that UTC should be the default, but rather running as PHP used to without any regard for a timezone should be the default. Since many people simply don't understand the ramifications of needing to add daylight saving management into their applications. Treat a simple UTC default as 'server clock' so that 6PM is 6PM any time of the year and many of the problems go away?
Only enable timezone management when you need to start to take care of users in different timezones at which time one is forced to manage the shifts of time properly. Why do the people who are only running with local time need to worry? The second you start to use timezones you need to set things up properly yourself!
Add of cause the fact that it's not just using DateTime with a timezone that causes a problem, but the bugs which remain in it are another area that can cause problems.
-- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
