Stanislav Malyshev wrote:
LS>>It seems evident that the old magic never worked reliably exactly for those
LS>>people that are now seemingly adversly affected by the current changes. Its
It doesn't seem evident to me. For me it worked flawlessly and did
exactly what I wanted it to do - show current time on the machine in the
format I tell it to.
You honestly claim that the current code makes it possible to write
portable code? Anyone who has ever tried to write a calendar app in PHP
will tell you that timezone handling is beyond subpar in PHP.
What is the case is that you are obviously in one of those timezones
that overlap with another. As such you have to be greatful that things
work right now. However by the same token its likely that for other
people also in IDT things are not working at all right now.
The only way to make sure that an application which relies on timezones
will _really_ be portable is to stop relying on OS code. This may in
fact mean that in the future sysadmins will have to configure a php.ini
setting when they install PHP, just as they do with other settings today.
So while I acknowledge that the switch will not be without growing pains
and while I acknowledge we should reduce those growing pains to a
minimum it seems evident to me that one day we will need to force this
switch into our users or we will have to maintain an old "maybe you are
lucky" and a "proper" implementation .. which seems like a waste of
ressources to me.
What I was raising as a question in my email was one of timing. For
example there could be an interim period where we do maintain the
duplicate code and then remove the old stuff, in php6 for example, at a
later point in time.
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
