Re: New Datetime class problem

From: Date: Sun, 05 Nov 2006 17:09:54 +0000
Subject: Re: New Datetime class problem
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-26350@lists.php.net to get a copy of this message
( This should have been to the pigging list !!!! sorry Ilia ) Ilia Alshanetsky wrote:
You can use old PHP too, or modify the source code, it is "open source" after-all.
Come on, that can't be the solution. Think about hosting companies for example.
They as a rule use old versions, in fact I bet you'd be hard pressed to find a big or even a medium size hosting company offering PHP 5.2 just now. So you have plenty of time to fix your code.
The main problem here Ilia is that people HAVE to fix their code JUST IN CASE the host updates. Some people will not even know they have a problem because they are using a third party application and then they will not know how to fix it IF their host updates. Since it would seem that most hosts have not even switched to PHP5 anyway, this is probably all academic anyway, but we have been here before, with versions of PHP released that broke a large number of applications and it got to the state that host WOULD NOT update in case it broke something. DateTime is just another example of the fact that PHP has no management of conventions and these get changed version to version. We NEED a mechanism to pinch back common function names that does not break existing applications simply because the vast number of users have no knowledge that there is a problem! -- Lester Caine - G8HFL ----------------------------- L.S.Caine Electronic Services - http://home.lsces.co.uk Model Engineers Digital Workshop - http://home.lsces.co.uk/ModelEngineersDigitalWorkshop/ Treasurer - Firebird Foundation Inc. - http://www.firebirdsql.org/index.php

« previous php.internals (#26350) next »