Stanislav Malyshev wrote:
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.
Again timing is a separate issue, just talking about the long term here ..
On one side you have people writing single timezone applications. Some
of them exist to day, some of them will be written in the future. I
guess aside from the inconsistent daylight saving time handling in the
current functions they can write working applications.
Anyone else is screwed right now.
So one approach could be to add code that helps the other guys. Problem
solved. However we then have duplicate code to deal with almost the same
problem: dates.
Now the new code does cause problems for some (certainly not a majority
of people) and this needs to be taken into account. However if these
people do set things in their php.ini file they have _no_ problem at
all. So the growing pains boils down to forcing users/admins to set a
single php.ini setting and suddenly we do not have any code duplication.
I think we have done things like this in the past. This also aliviates
the obvious user confusion about the existance of duplicate functions,
aside from not wasting ressouces on the code maintainance.
Do you think this is not even a feasible vision for the future?
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
