Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38035
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.250 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=Cjsxd7T0wUw3QqZ8soU1dB5smbOIeAOmkGyXy6YC71a/aCO1BLocpErrn9tvdjS9BH99Z3L3uyzlum0mg6mAAfiQwMA85RJZOsouWmSLyMGq8XVpH4oqy7taY/lK6s58LxLxeT1/ExpK4IDx3OwWPZQIoh+QOOVrShdPzUXPiA0=
Message-ID: <462e563f0805311027k4c6309d1l4fa631cfd974384f@mail.gmail.com>
Date: Sat, 31 May 2008 18:27:49 +0100
To: "Larry Garfield" <larry@garfieldtech.com>
Cc: internals@lists.php.net
In-Reply-To: <200805311201.09416.larry@garfieldtech.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_9632_2564869.1212254869431"
References: <AD0175DD650649EBA7BCD3E4278EC654@pc>
	 <C5339B1741FB4C719E42CF3119E1D4E9@pc>
	 <462e563f0805310602t350f8c29p96357b65aef2d14a@mail.gmail.com>
	 <200805311201.09416.larry@garfieldtech.com>
Subject: Re: [PHP-DEV] Alternative to multiple namespaces per file
From: letssurf@gmail.com ("James Dempster")

------=_Part_9632_2564869.1212254869431
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Sat, May 31, 2008 at 6:01 PM, Larry Garfield <larry@garfieldtech.com>
wrote:

> On Saturday 31 May 2008, James Dempster wrote:
> > I would agree with you, I think namespaces should wait for a later
> version.
> > Maybe 6 or even later. I believe there are many problems that need to be
> > sorted be namespaces hit release.
> >
> > Maybe we could do something like so.
> >
> > namespace Fully::Qualified::Class::Name class Declaration extends
> Whatever
> > implents MyInterface { }
> >
> > I have reservations in using :: as a resolution operator which can easily
> > clash with normal class space usage.
> >
> > Is it too late to have these discussions?? It seems I missed the big
> > namespace discussions on the mailing list and things have already gone
> > ahead.
> >
> > /James
>
> Unfortunately it probably is.  I recall someone did raise the
> ClassName::staticMethod() vs. Namespace::function() collision problem
> months
> ago, and the response at the time was "Pfft, like who uses classes and
> functions in the same project, anyway?"
>
> (Of course, the answer is "well I do" but I've long since learned that such
> answers don't carry much weight around here, so I mostly just read to see
> where the language is going rather than to influence it.  So I've just
> resigned myself to not being able to use namespaces in PHP.)
>

It's things like this that make me worry about the future of PHP. The elite
few pushing out lots of developers. :(

If namespaces are going to be problematic then lets wait for version 6.
It would also give more time for namespaces to be thought out properly.
I feel that namespaces in it's current form is a half arsed attempt to force
something into the language.


>
> --
> Larry Garfield                  AIM: LOLG42
> larry@garfieldtech.com          ICQ: 6817012
>
> "If nature has made any one thing less susceptible than all others of
> exclusive property, it is the action of the thinking power called an idea,
> which an individual may exclusively possess as long as he keeps it to
> himself; but the moment it is divulged, it forces itself into the
> possession
> of every one, and the receiver cannot dispossess himself of it."  -- Thomas
> Jefferson
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
/James

------=_Part_9632_2564869.1212254869431--