Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35699
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 21 Feb 2008 10:55:44 -0800
Message-ID: <698DE66518E7CA45812BD18E807866CE014A8F72@us-ex1.zend.net>
Thread-Topic: [PHP-DEV] RFC: Traits for PHP
Thread-Index: Ach0uDhO2hI+FVJPQk2hXf+T/0RaVAAAo2KQ
References: <001c01c87264$3c01b4e0$b4051ea0$@de> <698DE66518E7CA45812BD18E807866CE014A8D9D@us-ex1.zend.net> <A8D5F2E2-AAD0-45A7-8BFA-0A95DF42E514@pooteeweet.org> <698DE66518E7CA45812BD18E807866CE014A8F1E@us-ex1.zend.net> <E772BD58-7817-4EC6-A837-E220D823324E@pooteeweet.org>
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>
Cc: <php@stefan-marr.de>,
	<internals@lists.php.net>,
	=?iso-8859-1?Q?Marcus_B=F6rger?= <helly@php.net>,
	=?iso-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>,
	"Sebastian Bergmann" <sb@sebastian-bergmann.de>,
	"Alexandre Bergel" <alexandre@bergel.eu>,
	"Falko Menge" <falko.menge@hpi.uni-potsdam.de>,
	"Sara Golemon" <pollita@php.net>,
	<derick@php.net>
Subject: RE: [PHP-DEV] RFC: Traits for PHP
From: andi@zend.com ("Andi Gutmans")


> -----Original Message-----
> From: Lukas Kahwe Smith [mailto:mls@pooteeweet.org]
> Sent: Thursday, February 21, 2008 10:32 AM
> To: Andi Gutmans
> Cc: php@stefan-marr.de; internals@lists.php.net; Marcus B=F6rger;
> Johannes Schl=FCter; Sebastian Bergmann; Alexandre Bergel; Falko =
Menge;
> Sara Golemon; derick@php.net
> Subject: Re: [PHP-DEV] RFC: Traits for PHP
>=20
>=20
> On 21.02.2008, at 19:09, Andi Gutmans wrote:
>=20
> > I don't think so. I think the value here is not copy&paste but to be
> > able to encapsulate some functionality which a class can be
> > decorated with. Giving a basic storage mechanism to that would be
> > very beneficial in a large amount of uses. Again, I am proposing
> > private storage only which would be for internal use-only by the
> > decorating methods.
>=20
> if someone desperately needs that they could just write a method with
> a static variable.

Not really because if you want a container shared across the methods it =
wouldn't be very feasible. I'm sure there are some hacks you can do but =
I just think it'd be a pretty common use case.

Stefan, you have done a lot of research in this area and I assume have =
also looked at the most common=20
use-cases where this functionality is used in other languages. What is =
your sense?

> again i prefer to keep the feature as simple as possible without
> crippeling it the point of not being useful.

This suggestion is actually geared towards the opposite of crippling =
(private property is actually an addition). I actually think this is =
something which would be a very common use case for our users.

Btw, the 2nd part where I recommend brainstorming about a slightly =
stronger contract would actually also drive more towards simplicity.=20

In any case, I think we all agree this is a good thing to have in PHP. I =
am not advocating the opposite but I would like to explore some of these =
use-cases and options for a slightly stricter contact.

Andi