Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51263
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.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=oZVdLVtwKbJKcRlUuv+wICJ5u1GRFA85cO/gLh6oQPP2p6nm56cGgKTKR/SNcKZZop
         LRMBJJKCtpMKX8JocU4siTwYm5aAxGXK+eLoneOF1HDyQNXPKw8fvgQOYhZhe+LGf87m
         0WSOZaMAAjFb3u2Ugcg2yumW5E+AiOpY0dFbs=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=eNQYS5-4Zs6BOtfezdexDsxp5zc=+WZzeceuf@mail.gmail.com>
References: <AANLkTin3tG3yqFzKxSqNBe6-3k=K2XSYbQmJJYaJnFiy@mail.gmail.com>
	<1294276068.10675.3.camel@guybrush>
	<AANLkTikdFbNaR_PT8Lnsy-6rtWjT_6uy0dPyOiBGpfE0@mail.gmail.com>
	<AANLkTim725JWw=wcCC7rLY=eyVJKrfPUk2bnWhr_AeFh@mail.gmail.com>
	<4D283A96.3090908@yahoo.com.au>
	<AANLkTi=eNQYS5-4Zs6BOtfezdexDsxp5zc=+WZzeceuf@mail.gmail.com>
Date: Thu, 13 Jan 2011 12:22:20 -0300
Message-ID: <AANLkTi=m2DFLojhyXtN0OV1C9zNYCcUnmsDF4_THJ9Ek@mail.gmail.com>
To: Martin Vium <martin@sitevision.dk>
Cc: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>, internals@lists.php.net
Content-Type: multipart/alternative; boundary=0015175cd59843a51c0499bbe261
Subject: Re: [PHP-DEV] RFC: about class names as values
From: martinscotta@gmail.com (Martin Scotta)

--0015175cd59843a51c0499bbe261
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

I don't know how the internal development process of PHP works.

First at all: was this feature approved?

if that is a "yes"...
is this feature going to be scheduled for some release?
Is it supposed that I will submit a patch?

Thanks you all,
 Martin Scotta


On Sun, Jan 9, 2011 at 11:07 AM, Martin Vium <martin@sitevision.dk> wrote:

> I think adding a magic constant or method for getting the class name woul=
d
> be usefull in many scenarios, when referencing a specific class (e.g.
> factories, configurations). It would also work well with namespaces and
> refactoring tools e.g.:
>
> $mock =3D $this->getMock('\\My\\Custom\\Namespace\\MyClass');
>
> vs.
>
> use My\Custom\Namespace\MyClass;
> $mock =3D $this->getMock(MyClass::CLASS);
>
> On 8 January 2011 11:21, Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
> wrote:
>
> > I think doing something like this is a good idea for classes and
> > interfaces.
> >
> > Ben.
> >
> >
> >
> >
> > On 7/01/11 1:16 AM, Martin Scotta wrote:
> >
> >> Yes, my intention was to only add a magic constant with the class,
> similar
> >> to this
> >>
> >> namespace Bar {
> >>   class Foo {
> >>     const KLASS =3D __CLASS__;
> >>   }
> >> }
> >>
> >> namespace Buzz {
> >>   use \Bar\Foo as BazFoo;
> >>
> >>   class Bar extends BazFoo {
> >>     const KLASS =3D __CLASS__;
> >>   }
> >>
> >>   $bar =3D new Bar;
> >>   $baz =3D new BazFoo;
> >>
> >>   var_dump( get_class($baz), BazFoo::KLASS);
> >>   var_dump( get_class($bar), Bar::KLASS );
> >> }
> >>
> >> This is 100% valid PHP 5.3.3 code, but that includes a lot of effort
> from
> >> the developer. Someone miss to include the KLASS constant on a class a=
nd
> >> the
> >> result is undefined.
> >>
> >> If that PHP could add a magic constant --named CLASS or whatever you
> >> like--
> >> to each class it will reduce the amount of class names hardcoded onto
> >> strings, probably to zero.
> >>
> >> The only issue that I found today is related to interfaces. I'm not su=
re
> >> if
> >> they should include this sort of magic constant, but I would rather
> >> include
> >> them just for consistency but, as I previously said, I'm not sure abou=
t
> >> this
> >> one.
> >>
> >>  Martin Scotta
> >>
> >>
> >> 2011/1/5 John LeSueur<john.lesueur@gmail.com>
> >>
> >>
> >>>
> >>> 2011/1/5 Johannes Schl=FCter<johannes@php.net>
> >>>
> >>>  On Wed, 2011-01-05 at 21:53 -0300, Martin Scotta wrote:
> >>>>
> >>>>> $obj =3D newInstance( MyClass ); // notice. undefined constant MyCl=
ass
> >>>>>
> >>>>
> >>>> This describes the major change with your idea.
> >>>>
> >>>> What happens if a constant MyClass exists?
> >>>>
> >>>> Another question is something like this:
> >>>>
> >>>> <?php
> >>>> function  factory($class) {
> >>>>    return new $class();
> >>>> }
> >>>>
> >>>> factory( SomeClass );
> >>>> ?>
> >>>>
> >>>>
> >>>> To proper support this we'd have to make classes first class element=
s.
> >>>> For making this consistent it would make sense to make functions fir=
st
> >>>> class elements. And best drop the $ in front of variables and create=
 a
> >>>> new language. Everything else becomes a mess.
> >>>>
> >>>> johannes
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> PHP Internals - PHP Runtime Development Mailing List
> >>>> To unsubscribe, visit: http://www.php.net/unsub.php
> >>>>
> >>>>
> >>>>  I think he's actually proposing creating for each class the magic
> class
> >>> constant CLASS, so your example becomes:
> >>>
> >>>
> >>> <?php
> >>>
> >>> function factory($class) {
> >>>     return new $class();
> >>> }
> >>>
> >>> factory( SomeClass::CLASS );
> >>>
> >>> ?>
> >>>
> >>> This is actually doable without a magic class constant, but requires =
a
> >>> function or class constant to be declared in each class.
> >>>
> >>> <?php
> >>> class SomeClass {
> >>>     const CLASS =3D __NAMESPACE__ . '\' . __CLASS__;
> >>>     static function getNameWithNSPath()
> >>>     {
> >>>         return __NAMESPACE__ . '\' . __CLASS__;
> >>>     }
> >>> }
> >>>
> >>>
> >>> factory( SomeClass::getNameWithNSPath() );
> >>> ?>
> >>>
> >>> Perhaps this could be simplified with traits, if __NAMESPACE__ and
> >>> __CLASS__ work in traits that way. In fact, that's an interesting
> >>> question,
> >>> what is __NAMESPACE__ in a trait defined in one namespace, then used =
in
> a
> >>> class in a different namespace?
> >>>
> >>> I think the point is that the factory function could exist without an=
y
> >>> knowledge of the namespaces of the classes it would work on. Then,
> >>> somewhere
> >>> else where the class has been aliased or is otherwise accessible
> without
> >>> the
> >>> full namespace path, the developer wouldn't need to specify the full
> >>> namespace path to the factory, but could ask the class itself what it=
's
> >>> full
> >>> namespace path was. I don't know that I agree with the idea, but I
> don't
> >>> think it requires making classes first class elements.
> >>>
> >>> John
> >>>
> >>>
> >>>
> >>
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: http://www.php.net/unsub.php
> >
> >
> >
>
>
> --
> Mvh
> Martin Vium
> Senior System Arkitekt
> Sitevision
>

--0015175cd59843a51c0499bbe261--