Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40378
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain horde.org designates 75.144.171.129 as permitted sender)
Message-ID: <20080908175747.15286prnn4siyubk@technest.org>
Date: Mon, 08 Sep 2008 17:57:47 -0400
To: internals@lists.php.net
References: <48C59D5C.4050507@chiaraquartet.net>
In-Reply-To: <48C59D5C.4050507@chiaraquartet.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Dynamic Internet Messaging Program (DIMP) H3 (2.0-cvs)
Subject: Re: [PHP-DEV] namespace examples (solving name resolution order
	issues)
From: chuck@horde.org (Chuck Hagenbuch)

Quoting Greg Beaver <greg@chiaraquartet.net>:

> Part 3:
> judgment of value
>
> Current approach:
> advantages:
> 1) internal classes resolve very fast
> disadvantages:
> 1) potential unexpected name resolution to internal class when
> namespaced classname exists
>
> New approach:
> advantages:
> 1) code runs the same regardless of load order or autoload
> disadvantages:
> 1) serious performance slowdown on each internal class name resolution

In my opinion the unexpected name resolution to internal classes is a =20
serious flaw in the current namespace implementation, and will cause a =20
lot of confusion or (in my case) avoiding namespaces altogether. The =20
clincher for me is that the performance ramifications can be solved =20
with the exact same workaround that is currently necessary for all =20
user-defined classes (use ::Exception) AND - in PHP user-defined =20
classes are far more common and numerous than internal classes.

So I would be extremely happy to see this change go into PHP 5_3. =20
Thanks, Greg!

-chuck