Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35840
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.162 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 27 Feb 2008 20:14:17 -0800
Message-ID: <698DE66518E7CA45812BD18E807866CE01506473@us-ex1.zend.net>
Thread-Topic: [PHP-DEV] How to build a real Trait thing without exclusion and renaming
Thread-Index: Ach5tvPk65z+LicsSpO5LHlLSOg7xwACSJ4w
References: <47C317F4.2080301@stefan-marr.de> <698DE66518E7CA45812BD18E807866CE01506447@us-ex1.zend.net> <47C6253A.1070407@zend.com>
To: "Stas Malyshev" <stas@zend.com>
Cc: <php@stefan-marr.de>,
	"internals Mailing List" <internals@lists.php.net>
Subject: RE: [PHP-DEV] How to build a real Trait thing without exclusion and renaming
From: andi@zend.com ("Andi Gutmans")

> -----Original Message-----
> From: Stanislav Malyshev [mailto:stas@zend.com]
> Sent: Wednesday, February 27, 2008 7:07 PM
> To: Andi Gutmans
> Cc: php@stefan-marr.de; internals Mailing List
> Subject: Re: [PHP-DEV] How to build a real Trait thing without
> exclusion and renaming
>=20
> Hi!
>=20
> > trait MyDebug {
> > 	local $counter =3D 1;
>=20
> IIRC we don't have keyword "local". Why not "private" or "static"?

I wouldn't get too caught up on the naming at this point but rather the
functionality.

> > class MyClock {
> > 	use MyDebug *;
> > 	use MyTicks {
> > 		timeInTicks =3D inTicks;
>=20
> This looks like code which does assignment. How I am supposed to
> understand from it that a new method for MyClock API is born?
>=20
> In any case, why you need timeInTicks at all? If you need it public,
> why
> not write an accessor? It'd be better OO anyway, since MyClock's
> clients
> can't know about MyTicks's details or even its existence.

This is just an example of being able to alias a method from a trait.
Assuming two traits would use the same name this would give you the
ability to include it under a different name.
The point is we can alias but we can not remove.

Andi