Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49210
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.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=crj2gcQBTkwx6zU3W3Oa7/e2wU095a6me2ivPQcAFUcif0qEyr3fycQ3CG10hujaW/
         eJB32MbFplEX+yDE4EhoAQ4L3KA5vP1SUtOFBOCsNHbJMvf3E+bgAHxz2ot9zMRDzKZy
         8ul/ahsI7PJyiUDdgnUAPylwx/Zo85wmLY3aU=
MIME-Version: 1.0
In-Reply-To: <4C5B3C13.4080107@sugarcrm.com>
References: <AANLkTi=Qw0XheTbj6LpJs1D5N+hnsPYTuR115grx8WsR@mail.gmail.com>
	<4C5B3C13.4080107@sugarcrm.com>
Date: Fri, 6 Aug 2010 08:24:39 +0000
Message-ID: <AANLkTi=a3T_2opNPL-_wgyHQ5bWi=_KH-rPrU8Sx8iuQ@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Feature proposal: userland support for name 
	qualification
From: ignas.rudaitis@gmail.com (Ignas Rudaitis)

Hi,

well, my apologies for not making that clear enough. I suppose it
wouldn't require any runtime information, as this kind of construct
could be expanded at compile time.

For example:

<?php

namespace LibraryWithAVeryLongName;

// Setting up a service container, like Phemto, as of PHP 5.3.3
$container->willUse('LibraryWithAVeryLongName\Cache\FileCache')
          ->willUse('LibraryWithAVeryLongName\Routing\CachingRouter')
          ->willUse('LibraryWithAVeryLongName\Parsing\CachingParser');
// tens of similar declarations follow

// Mentioning a class name in an exception message
throw new \InvalidArgumentException('The first argument must be an
array or an instance of LibraryWithAVeryLongName\Collections\List');

?>

Now if there was a COMPILE-TIME construct for expanding unqualified
names and "quoting" them, i.e. turning them into string literals, then
the 'LibraryWithAVeryLongName' prefix would be redundant, because it's
already declared as the current namespace.

In Java, there is the Foo.class syntax. C# has typeof(Foo). So
something like class(Foo) would be nice to have in PHP. Even if such
long namespace names as in the example don't make sense, deeply-nested
ones do, so that's hardly an exaggeration.

Now, an example using the proposed syntax:

<?php

namespace LibraryWithAVeryLongName;

$container->willUse(class(Cache\FileCache))
          ->willUse(class(Routing\CachingRouter))
          ->willUse(class(Parsing\CachingParser)); // and so on

use  LibraryWithAVeryLongName\Collections\List;

throw new \InvalidArgumentException('The first argument must be an
array or an instance of ' . class(List));

?>

And of course, class(Foo) doesn't have to be the exact syntax.

On 8/5/10, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>> unqualified aliases, it would be useful to extend this functionality
>> to string references to these classes/functions/constants as well.
>
> It would require to carry "namespace context" around with every
> function/class in runtime and for me the usecase is not clear. Can you
> describe more in detail what you try to do and why you need runtime
> resolution for it?
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>

-- 
Sent from my mobile device