Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35742
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: Sat, 23 Feb 2008 00:30:30 -0800
Message-ID: <698DE66518E7CA45812BD18E807866CE014A9358@us-ex1.zend.net>
Thread-Topic: [PHP-DEV] RFC: Traits for PHP
Thread-Index: Ach1d2DXQ+EVhLRTTZeDdn3uxtCmKgAfbjBw
References: <001c01c87264$3c01b4e0$b4051ea0$@de> <173732199.20080219175837@marcus-boerger.de> <1203452909.24580.9.camel@localhost> <1e12984d0802191323o710c6b8ej3a54af7901cf35f1@mail.gmail.com> <47BB4AC9.9070701@zend.com> <1e12984d0802191346x7c145d7fp14c01ec4e5993779@mail.gmail.com> <47BB4F49.1030904@rooftopsolutions.nl> <1e12984d0802191359p4f21c3acrdff4b86adfb4bf3@mail.gmail.com> <1495054633.20080220205951@marcus-boerger.de> <1e12984d0802201243gfa51f01i311891e8965ed51e@mail.gmail.com> <9EE7F229-0710-48E8-9A26-DC8031AF8979@pooteeweet.org> <1985981545.20080222134413@marcus-boerger.de> <47BEE001.9080602@chiaraquartet.net> <B9A7A220-6AB6-4511-8587-19F520EA5885@pooteeweet.org> <47BF0465.3080700@zend.com>
To: "Stas Malyshev" <stas@zend.com>,
	"Lukas Kahwe Smith" <mls@pooteeweet.org>
Cc: "Gregory Beaver" <greg@chiaraquartet.net>,
	"Marcus Boerger" <helly@php.net>,
	<php@stefan-marr.de>,
	"Evert|Rooftop" <evert@rooftopsolutions.nl>,
	<internals@lists.php.net>
Subject: RE: [PHP-DEV] RFC: Traits for PHP
From: andi@zend.com ("Andi Gutmans")

> -----Original Message-----
> From: Stanislav Malyshev [mailto:stas@zend.com]
> Sent: Friday, February 22, 2008 9:21 AM
> To: Lukas Kahwe Smith
> Cc: Gregory Beaver; Marcus Boerger; php@stefan-marr.de; Evert|Rooftop;
> internals@lists.php.net
> Subject: Re: [PHP-DEV] RFC: Traits for PHP
>=20
> Hi!
>=20
> > A trait may contain methods and properties. When importing a trait
> into
> > a class, all methods and properties are imported in a way that makes
> > them only visible within the trait (I dont like the use of "private"
>=20
> How you are going to do that?

I think it's possible to do this but I haven't had time to dive deeper
in the past couple of days.

In my opinion the benefits of doing Traits in this way would be
significant.
You would still get the benefits of the original Traits proposal but it
would provide stronger encapsulation and less potential for breakage (on
par with typical OO polymorphism).
In addition I really believe that enabling state is extremely important
to make this a commonly useful feature (either via "private" or via a
"local" like Stefan suggested).

I won't be back at work until Tuesday but I will try and find some time
to figure out if this can be implemented. I am pretty sure it can if
during compilation of the Trait we mangle the properties&methods similar
to private properties&methods using the Trait's name; and then when we
flatten into a class then for the methods we expose we make sure the
mangled methods use the new method's op_array. This should not be too
hard and as Traits flattening does not require the same semantics as
inheritance I think it should be quite doable.

Bed time over here but I wanted to drop a short note so you didn't think
I dropped of the face of the planet in the midst of this interesting
discussion :)
Andi