Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31204
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.82.229 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=tJ6IFx7zLZ51EytpL6zid8nM3YHtF29xoDqs7DqikismcKJl7GnIwdpobdpeFzH5+Q7o05bKks3y1XIICNLjAOLzJ+MtWLjAmVpQ8CmMMBawl6aXW6CybaXB3/+ps8MkaXWCZ0MP5zCT0UVU9KzTD2btBLLuSyr7jzqgZTuEul8=
Message-ID: <b5f7bf6c0707230918i3fbb1831sade911ce577b006d@mail.gmail.com>
Date: Mon, 23 Jul 2007 12:18:44 -0400
Sender: david.coallier@gmail.com
To: "Jeremy Privett" <jeremy@peak8solutions.com>
Cc: "=?ISO-8859-1?Q?Nicolas_B=E9rard-Nault?=" <nicobn@php.net>, 
	"Derick Rethans" <derick@php.net>, 
	"=?ISO-8859-1?Q?David_Z=FClke?=" <dz@bitxtender.com>, 
	"PHP Internals" <internals@lists.php.net>
In-Reply-To: <E996AAF4A714DF4D9BD59E9418957A2128CD37@peak8sbs.peak8solutions.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <46A31D95.2080407@fischer.name>
	 <E996AAF4A714DF4D9BD59E9418957A2128CD19@peak8sbs.peak8solutions.local>
	 <46A4661A.6080202@zend.com> <200707231140.55535.pstradomski@gmail.com>
	 <46A4BA4F.6090506@dealnews.com>
	 <40CA6572-030F-43E2-8706-64D1167C527C@bitxtender.com>
	 <alpine.DEB.0.98.0707231646120.27483@kossu.ez.no>
	 <30bd80240707230902m5084b6d9te4489173675f22ec@mail.gmail.com>
	 <E996AAF4A714DF4D9BD59E9418957A2128CD37@peak8sbs.peak8solutions.local>
Subject: Re: [PHP-DEV] Question about Namespace patch
From: davidc@php.net ("David Coallier")

On 7/23/07, Jeremy Privett <jeremy@peak8solutions.com> wrote:
> Yes, because that's ABSOLUTELY the way to respond to the community that h=
as continued to support PHP. If that is what this discussion is going to de=
grade to, you're essentially saying "Please, gives us feedback but we're no=
t 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 o=
f 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=
=E9rard-Nault
> Sent: Monday, July 23, 2007 10:03 AM
> To: Derick Rethans
> Cc: David Z=FClke; PHP Internals
> Subject: Re: [PHP-DEV] Question about Namespace patch
>
> Despite all the comments made on this list by countless people, it's stil=
l
> 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=FClke 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 bring=
ing
> > your
> > > > classes into the global name space.  The nice thing about namespace=
s
> > 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 =3D new SQLAlchemy::Transaction.
> > >
> > > Oh yes, sure, that must be the main point about namespaces - I can us=
e
> > "::"
> > > 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=E9rard-Nault (nicobn@gmail.com)
> =C9tudiant D.E.C. Sciences, Lettres & Arts
> C=E9gep 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.

--=20
David Coallier,
Founder & Software Architect,
Agora Production (http://agoraproduction.com)
51.42.06.70.18