Re: Question about Namespace patch

From: Date: Mon, 23 Jul 2007 16:18:44 +0000
Subject: Re: Question about Namespace patch
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to internals+get-31204@lists.php.net to get a copy of this message
On 7/23/07, Jeremy Privett <jeremy@peak8solutions.com> wrote:
Yes, because that's ABSOLUTELY the way to respond to the community that has continued to support PHP. If that is what this discussion is going to degrade to, you're essentially saying "Please, gives us feedback but we're not listening." If this is the case, then I'll keep in mind and make sure it's known that bringing your issues and feedback to the PHP Devs is such a lovely waste of time and energy. Thanks. --- Jeremy Privett Software Developer Peak8 Solutions -----Original Message----- From: nicobn@gmail.com [mailto:nicobn@gmail.com] On Behalf Of Nicolas Bérard-Nault Sent: Monday, July 23, 2007 10:03 AM To: Derick Rethans Cc: David Zülke; PHP Internals Subject: Re: [PHP-DEV] Question about Namespace patch 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 <derick@php.net> 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 (nicobn@gmail.com) Étudiant D.E.C. Sciences, Lettres & Arts Cégep de Sherbrooke Homepage: http://nicobn.googlepages.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
Plus ca change, plus c'est pareil. -- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18

« previous php.internals (#31204) next »