Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54131
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender)
MIME-Version: 1.0
Reply-To: RQuadling@GMail.com
In-Reply-To: <4E29949C.9020209@gmail.com>
References: <4E29949C.9020209@gmail.com>
Date: Fri, 22 Jul 2011 16:40:51 +0100
Message-ID: <CAKUjMCWWmhkQTMLoof76nFZEZs80cz4KFgKtw5UzsX6XwFMoVw@mail.gmail.com>
To: Alex Howansky <alex.howansky@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] 5.4a2 trait attribute name conflict resolution
From: rquadling@gmail.com (Richard Quadling)

On 22 July 2011 16:17, Alex Howansky <alex.howansky@gmail.com> wrote:
>
> Hello folks,
>
> I've just grabbed 5.4a2 to play with traits. I've found some behaviour wh=
ich
> I'm not sure is a bug, an inconsistency, or a design decision.
>
> Consider a trait and a class that implements it but also overrides both a
> trait method and a trait attribute:
>
> trait foo
> {
> =C2=A0 =C2=A0 public $zoo =3D 'foo::zoo';
> =C2=A0 =C2=A0 public function bar()
> =C2=A0 =C2=A0 {
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 echo "in foo::bar\n";
> =C2=A0 =C2=A0 }
> }
>
> class baz
> {
> =C2=A0 =C2=A0 use foo;
> =C2=A0 =C2=A0 public $zoo =3D 'baz::zoo';
> =C2=A0 =C2=A0 public function bar()
> =C2=A0 =C2=A0 {
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 echo "in baz::bar\n";
> =C2=A0 =C2=A0 }
> }
>
> $obj =3D new baz();
> $obj->bar();
> echo $obj->zoo, "\n";
>
> We get:
>
> in baz::bar
> foo::zoo
>
> It seems this is not correct and that it should be:
>
> in baz::bar
> baz::zoo
>
> The traits RFC pretty clearly states that if a class method conflicts wit=
h a
> trait method then the trait method will be ignored, which is what's
> happening, but it says nothing about what happens to attributes in that s=
ame
> condition. Is this a bug?
>
> Thanks,
>
> --
> Alex Howansky
>
>

In my limited understanding, a trait is sort of composited at compile
time (ish). As properties are dynamic (ish), they will overwrite. Just
like an inherited class will overwrite public properties in their
parent class.

--=20
Richard Quadling
Twitter : EE : Zend : PHPDoc
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY : bit.ly/lFnVea