LS>>You honestly claim that the current code makes it possible to write portable LS>>code? Anyone who has ever tried to write a calendar app in PHP will tell you LS>>that timezone handling is beyond subpar in PHP.
I wrote "did exactly what I wanted it to do - show current time on the machine". Yes, it was honestly portable - on each machine that PHP ran it showed the exact time that was on system's clock. It can be it was not fit for multiuser multitimezone calendar app - so what? Did I ever say you must use date() for it? Or that you can't improve date() to work with it? Sure you can. Just don't break the working parts. You seem to concentrate on only application you need and ignore the fact that there are other applications that have different needs. LS>>overlap with another. As such you have to be greatful that things work right LS>>now. However by the same token its likely that for other people also in IDT LS>>things are not working at all right now. Which things? Can you point me to the place in IDT timezone when date() doesn't show system's date on pre-5.1 PHP? No, you can't, because there's no such place. LS>>The only way to make sure that an application which relies on timezones will LS>>_really_ be portable is to stop relying on OS code. This may in fact mean If you want to build your own timezone handling - fine with me. I don't see why it should break much larger class of apps that never needed to work with multiple timezones - they need only one timezone, and that'd one that is installed and configured on the system. LS>>So while I acknowledge that the switch will not be without growing pains and That's not "growing pains". That's breaking working code pains. LS>>seems evident to me that one day we will need to force this switch into our LS>>users or we will have to maintain an old "maybe you are lucky" and a I don't see any need to force users into anything they don't need just because you seem to like the new code. Users don't care how much you love the code, they care if it works - and now it does not, at least not for the atsk of printing current date with date() call. -- Stanislav Malyshev, Zend Products Engineer [EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
