Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53341
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=JtKhYpD/oB6IEiwzHOm8DtW3nu/5rU/iSwXObcBV9PmdBvHjSsmBKb5xIgz4Ici72O
         tVQGwEAGDQJycpVwo6RrTsjFRo5dcuEvTzsnKnVIYkhIBDzJzNJwvIKiQXv21cCS8VrI
         yzDvCsjYxIZenFi2z5YZXZmldEWoxBzfq+seo=
MIME-Version: 1.0
In-Reply-To: <BANLkTimj5U80D93R9civLppCGCpBQjMTKA@mail.gmail.com>
References: <BANLkTi=gMaWi=bYGfj33rEROws7rYKFP3g@mail.gmail.com>
	<4DF8DC94.5060009@sugarcrm.com>
	<BANLkTi=GaiXg_SX=4Ts=-c91ryNO_AiPfA@mail.gmail.com>
	<BANLkTinbyR2A9sZhUyoTqLUF1j1NKBSzqg@mail.gmail.com>
	<BANLkTimkJP9h00DneBSdmBbE2Km4Pr_F3g@mail.gmail.com>
	<4DFA31EF.1050900@sugarcrm.com>
	<BANLkTimj5U80D93R9civLppCGCpBQjMTKA@mail.gmail.com>
Date: Thu, 16 Jun 2011 19:54:12 +0200
Message-ID: <BANLkTikHXuc4NzFtwOG=egoS8Aae_Doj9Q@mail.gmail.com>
To: RQuadling@gmail.com
Cc: Stas Malyshev <smalyshev@sugarcrm.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=000e0cd733f8f043f604a5d7f41a
Subject: Re: [PHP-DEV] Getting a list of registered namespaces.
From: tyra3l@gmail.com (Ferenc Kovacs)

--000e0cd733f8f043f604a5d7f41a
Content-Type: text/plain; charset=UTF-8

On Thu, Jun 16, 2011 at 7:48 PM, Richard Quadling <rquadling@gmail.com>wrote:

> On 16 June 2011 17:40, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> > Hi!
> >
> > On 6/16/11 8:37 AM, Richard Quadling wrote:
> >>
> >> Maybe, but because of a lack of convention on naming, we have
> namespaces.
> >
> > No, we have namespaces not because we couldn't agree on naming
> convention,
> > but because any naming convention without namespaces would lead to ugly
> code
> > (which you call "sensible long names" but which rapidly stop being
> sensible
> > if you actually try to do it).
>
> I was joking.
>
> >
> >> So it would seem appropriate to have the ability to investigate a
> >> namespace to see what it contains and/or if it exists.
> >>
> >> Why? For exactly the same reasons you have class_exists(),
> >> interface_exists(), function_exists().
> >
> > Classes and functions actually exist as objects in the engine. Namespaces
> do
> > not. They are just parts of names. You can not instantiate a namespace,
> you
> > can not call a namespace. So these reasons do not apply.
>
>
> And now I understand. Thanks for that.
>
>
Okay, so namespaces doesn't exists for the engine, because they are added to
the classnames in compile-time, but we could add some --rX argument for the
php binary, which would iterate over the classes and functions and so for a
given extension, and fetch and list the introduced namespaces.
what do you think?

Tyrael

--000e0cd733f8f043f604a5d7f41a--