Hello Martin, the funny thing here is that obviously we cannot prefix things we have right now. Using namepsaces we would be free to enforce namespaces upon everyhting that's been built in and simply provide import. And if we really wanted to we could also have a "zend.ze1_compatibility_mode" like ini setting to import anything to the global space and voila - the php 6 code writers can go without and those who want to use php 5 stuff can easily do so. There won't be aproblem for namespaces users when imporint things to the global space.
marcus Saturday, November 26, 2005, 10:12:56 AM, you wrote: > On Sat Nov 26, 2005 at 09:5522AM +0100, Ron Korving wrote: >> > Speaking of this, I like Greg's suggestion about prefixing all internal >> > classes with PHP_. While there are certainly classes out there that are >> > prefixed with it, we could tell developers that starting with e.g. PHP 6 >> > the PHP_* class scope is reserved for the language core and must not be >> > used for any other purpose. >> >> Why would you, if you have namespaces? > Correct me if I'm wrong, but I got the impression that despite Jessie's > patch and Marcus' competence in all things C people are still unsure if > namespaces will make it into PHP 6. Thus having an alternative strategy > at hand seems wise. > Best, > - Martin Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
