Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35596
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender)
Date: Tue, 19 Feb 2008 15:34:08 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1028403632.20080219153408@marcus-boerger.de>
To: "Stefan Marr" <php@stefan-marr.de>
CC: "Mark van der Velden" <mark@dynom.nl>, 
	"PHP internals" <internals@lists.php.net>
In-Reply-To: <1e12984d0802190409g4fc04c88hd0ddf0f920706a66@mail.gmail.com>
References: <47BAB2A5.8050008@dynom.nl> <1e12984d0802190409g4fc04c88hd0ddf0f920706a66@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Traits for PHP
From: helly@php.net (Marcus Boerger)

Hello Stefan,

  a userland copy'n'paste does not allow to reuse already compiled opcodes.
Traits do at least conceptionally.

marcus

Tuesday, February 19, 2008, 1:09:24 PM, you wrote:

> Hi Mark,

>> If it doesn't affect performance *MUCH* then I'm all for it ! It can
>> bring better structure for complex designs. Also by reusing, I'm
>> assuming less memory will be needed for the code base which is beneficial.
> the current implementation does not save any memory compared to a
> user-level copy'n'past solution. But there might be the opportunity to
> optimize the op_array handling.

> The performance impact is almost the same for a trait usage as for
> inheritance or interface definitions. The only costly operation is
> copying the method body from the trait to the class where it is used.
> But this should be much cheaper than parsing the method for each
> single class, what would be necessary if one would use a good old
> copy'n'past approach.

> Kind Regards
> Stefan




Best regards,
 Marcus