Despite all the comments made on this list by countless people, it's still Stanislav's way or the highway. I don't want to sound negative but come on... this is getting ridiculous. Stanislav, why don't you just tell everybody that you'll stop answering because the patch will stay AS IT IS over your dead body anyway ? I think you'll save us all some time.
This discussion is endless and not productive. I can't speak for anybody here but I think a vote by all people who have commit access to php-src would clarify this issue once and for all so we can just move along. But that's just my 2 cents. On 7/23/07, Derick Rethans <[EMAIL PROTECTED]> wrote:
On Mon, 23 Jul 2007, David Zülke wrote: > Am 23.07.2007 um 16:25 schrieb Brian Moon: > > > > import SQLAlchemy::Column > > > import SQLAlchemy::Table > > > import SQLAlchemy::Join > > > import SQLAlchemy::ForeignKey > > > import SQLAlchemy::Session > > > import SQLAlchemy::Transaction > > > > Why use namespaces if you are going to do this? You are just bringing your > > classes into the global name space. The nice thing about namespaces IMO, is > > that I don't have to have a class named SQLAlchemy_Transaction. I can just > > have a class named Transaction in the SQLAlchemy namespace. I can then > > create a new object using $obj = new SQLAlchemy::Transaction. > > Oh yes, sure, that must be the main point about namespaces - I can use "::" > instead of "_" as a delimiter! Yay! You forgot that you can also move the "prefix" in front of the class name to "namespace prefix!" > Come on, you can't be serious. I sort of agree, I don't see how the current implementation is really useful for anything. regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
-- Nicolas Bérard-Nault ([EMAIL PROTECTED]) Étudiant D.E.C. Sciences, Lettres & Arts Cégep de Sherbrooke Homepage: http://nicobn.googlepages.com
