> > Then I have to ask both of you: why is there no mentioning in > the release notes or the upgrading guide regarding "Date" > being reserved for PHP now?
I was also curious as to that. Once again the release announcement (more precisely, the "upgrade" document) greatly understates the impact: "9b. Class constants in new PHP 5.1 extensions [...]in order to minimise pollution of the global namespace in PHP. Note that the new Date class exists at this point purely to allow the core date extension to adhere to the above convention, although extended functionality is planned for the the class in the future. " At least I'd say this is "diplomatic". You need to have a delicate understanding to even notice it, let alone understand the impact. And as to "polluting the global namespace" - well, this one is a supertanker that has just sunk at the shore of OOP. > The language/base library might want to reserve certain > simple classnames for itself. That is its right. Not, not even that when it comes to most obvious names like "Date" (or Page; User; Form...) or to commonly used ones (like Controller, Database, DAO, Singleton, Observer...). > But: Doing so in a minor release is absolutely bad timing. > It gets worde because there apparently has been _no_ > documentation of the fact at all. How shall our users > prepare themselves appropiately? Not even in a minor relase, but with the very last RCs. This is a smack in the face of all who even tried to keep up. -mp. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
