On Fri, 25 Nov 2005, Sascha Schumann wrote: > > No, as this breaks backwards compability. I have code written for this > > and that is going to be released. If the class constants are removed, > > you will break code that is out there. There were similar reasons why > > Wez didn't want to change the odd PDO method because people were running > > it production while PDO was not even beta - which is fine. But you can > > definitely not change code in a released version. > > Derick, the Date class is in "a released version" because you > sneaked it in through the backdoor. Activating a class in > the final RC was obviously wrong and you are very well aware > of the fact. Don't try to cover up now.
It's definitely not the most elegant way, I agree there. But there was also no sneaking as it was discussed months before, and it was actually Ilia who suggested doing it in PHP 5.1.0 and not 5.1.1. This code has been in CVS for about 5 months, but people didn't want to have it enabled as they didn't want to stall the release. The idea was to put it into 5.1.1 then. That is fine, but I think it's not fair to blame me for not having being allowed to put my code in there and thus creating the current problems. Besides that, using "Date" and "Timezone" as classnames are the most sensible names for those classes and I do not think we should have change that. regards, Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
