Having watched this thread intently for the past few weeks, we seem to be simply tripping over the semantics of it all, right?
Thinking a bit outside the box, how hard would it be to simply use both names, one as an alias of the other? In the end the documentation will probably need to outline how the PHP implementation differs from other popular languages. Just seems silly to let a semantics argument muddy the waters. --Tony ----- Original Message ---- From: Stanislav Malyshev <[EMAIL PROTECTED]> To: Marcus Boerger <[EMAIL PROTECTED]> Cc: PHP Internals List <internals@lists.php.net> Sent: Monday, August 20, 2007 12:09:34 PM Subject: Re: [PHP-DEV] Renaming namespaces to packages > interesting, we are still in prototype form....hmmm since when do we > commit proto types? I thought we are supposed to show patches until they > work as expected. So remembering the other new mails you guys wrote > recently....we might drop all of this again, we might rename all of it, we I don't think it's likely we drop it, as for renaming - wasn't it you who pushed for it? :) I'm all for leaving it as it is :) > might replace it completley... what the hell is going on here? Complex opensource project development? Frankly, I don't know how many people would even look at it if it was only in patch form - it's very big and complex patch. -- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
