Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60068
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c-xjvrYXNxfnMmP-eApBxJNzEu=EQ+7dmrbtzzsaezQCw@mail.gmail.com>
References: <4F89D4F1.8070009@ralphschindler.com> <CAF+90c-xjvrYXNxfnMmP-eApBxJNzEu=EQ+7dmrbtzzsaezQCw@mail.gmail.com>
Date: Tue, 17 Apr 2012 11:22:17 +0200
Message-ID: <CADyq6s+yuZzo12r4jd1q57F4rAJT0zVfdnr6t5_xJcDYsbuvAQ@mail.gmail.com>
To: Nikita Popov <nikita.ppv@googlemail.com>
Cc: Ralph Schindler <ralph@ralphschindler.com>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf303b3cd9d18f5104bddc7adb
Subject: Re: [PHP-DEV] New Feature: Fully qualified class name resolution as
 scalar with class keyword
From: ocramius@gmail.com (Marco Pivetta)

--20cf303b3cd9d18f5104bddc7adb
Content-Type: text/plain; charset=UTF-8

@Nicolas: wouldn't __CLASS__ introduce a bit of confusion with the existing
constant?

Marco Pivetta

http://twitter.com/Ocramius

http://marco-pivetta.com



On 17 April 2012 11:17, Nikita Popov <nikita.ppv@googlemail.com> wrote:

> On Sat, Apr 14, 2012 at 9:50 PM, Ralph Schindler
> <ralph@ralphschindler.com> wrote:
> > Hi all,
> >
> > There are many different use cases were in code we expect classes names
> as
> > arguments to functions as fully qualified names.  We do this in ZF a lot
> > with our Service Location and DI components, but also with our code
> > reflection API, etc.  A more interesting use case I would like to call
> out
> > is with PHPUnit, for example in a test, you might find this:
> >
> >  $mock = $this->getMock('A\Namespaced\ClassName');
> >
> > This becomes cumbersome when you are dealing with lots of strings about
> lots
> > of class names.  This is also an area where, currently, namespace
> > declaration and use statements offer no real support.
> >
> > The patch located here:
> >
> >
> https://github.com/ralphschindler/php-src/commit/02210d51851a96d723fbedcfc64cde9f9ae2b22a
> >
> > ... implements the ability for a developer to leverage the file's
> namespace
> > declaration and use statements to be able to produce a scalar (string) of
> > the class name that can be then used, for example, as an argument to a
> > function elsewhere.
> >
> > This overloads the "class" keyword, and by virtue of the existing usage
> of
> > "class" this feature is completely backwards compatible.  All existing
> tests
> > pass.  For example, the above PHPUnit snipped would become:
> >
> >  use A\Namespaced\ClassName;
> >  $mock = $this->getMock(ClassName::class);
> >
> > Another example with reflection:
> >
> >  use SomeOther\FullyNamespaced\ClassElsewhere as CE;
> >  $r = new ReflectionClass(CE::class);
> >
> > More examples from the test file:
> >
> >  namespace Foo\Bar {
> >    class Baz {}
> >    var_dump(Moo::CLASS); // "Foo\Bar\Moo"
> >  }
> >
> >  namespace {
> >    use Bee\Bop as Moo,
> >        Foo\Bar\Baz;
> >
> >    var_dump(Baz::class); // "Foo\Bar\Baz"
> >    var_dump(Boo::class); // "Boo"
> >    var_dump(Moo::CLASS); // "Bee\Bop"
> >    var_dump(\Moo::Class); // "Moo"
> >
> >    $class = Baz::class; // assign class as scalar to var
> >    $x = new $class;
> >    var_dump($x);  object(Foo\Bar\Baz)#1 (0) {}
> >  }
> >
> >
> > What do you guys think?
> Hey Ralph!
>
> I like the proposal :)
>
> A quick note on the patch: As the class name is compile-time
> resolvable it should in my eyes also be available as a
> `static_scalar`, so that it can be used in initialization lists:
>
>    public function doFoo($withClass = ABC::class) {
>        new $withClass; // or whatever
>    }
>
> To be available as both a `static_scalar` and a general `scalar` one
> should put the rule in the `common_scalar` section.
>
> What do you think?
>
> Nikita
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--20cf303b3cd9d18f5104bddc7adb--