Hello Stanislav, what the hell are you talking about? We had a namespace implementation and now we have a new one. One that for a lot of people here smells like packages. There are no three or more different ones. None of them was ever accepted or comitted. Actually I doubt that any of them was ever working. And oh the original implementation did not work either. And hey it had nestng and wasnt't bound to files.
Oh and speaking of your wiki again. Your wiki does not list any of the very hard limitations we have in the current implementations. And another thing. Why the hell would we want to implement packages and namespaces? Packages or namespaces as we have them right now are clearly a subset of the both the wiki and what people usually expect from namespaces. marcus Thursday, August 16, 2007, 2:04:01 AM, you wrote: >> This leaves the "Namespace" name available for future development if/as > Which means we officially declare PHP *doesn't* have namespaces (since > we reserve the right to develop it in the future, it's obvious we didn't > do it yet). Why it would be a good thing? >> needed (such as if the language were to show itself to need more than one >> namespace per file (or whatever the future may hold)). > So if we add braces we'd have to rename the keyword? >> It can still be touted that PHP has "namespace support" regardless of > Yes, we'd have to say "we have namespace support but we call it > packages" and when people ask "why?" we'd answer "well, because Java > calls it so" and people would say "ah, so when you were saying PHP is > not Java - *that's* what you meant!" > -- > Stanislav Malyshev, Zend Software Architect > [EMAIL PROTECTED] http://www.zend.com/ > (408)253-8829 MSN: [EMAIL PROTECTED] Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
