Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54193
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.177 as permitted sender)
MIME-Version: 1.0
Reply-To: php@stefan-marr.de
Sender: stefan.marr.de@gmail.com
In-Reply-To: <1311614509.2886.16.camel@guybrush>
References: <1311614509.2886.16.camel@guybrush>
Date: Mon, 25 Jul 2011 23:05:27 +0200
Message-ID: <CA+2ZKBZ9eg-wi_ja93uG8==c-03avBxxy0cokwA7GnpxGiA=Sg@mail.gmail.com>
To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>
Cc: PHP internals list <internals@lists.php.net>, gron@php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Reflection, Traits, Aliasing
From: php@stefan-marr.de (Stefan Marr)

Hi Johannes:

2011/7/25 Johannes Schl=FCter <johannes@schlueters.de>:

> Now I use reflection on this:
>
> $rc =3D new ReflectionClass('C');
> print_r($rc->getTraitAliases());
>
> Array
> (
> =A0 =A0[tc] =3D> T1::t1
> )

Great, that is nice.


> So far so nice but I'm missing the information where C::t1() is coming
> from. In the reflection code I'm currently iterating over
> ce->trait_aliases and can't find where I can get the information from.
> Actually I'd be even interested in getting all important methods and
> their origin. Stefan, do you know where I can find the information or
> would we have to store it additionally?
The functions do not store that information, so there are basically
only two approaches, I see:

Either, factoring out the code which is doing the flattening, conflict
resolution, and class composition into something which could be easily
shared by both the reflection and the engine, and then re-doing it on
demand in the reflection,
or we extend zend_function by an origin pointer.

Not sure what the better tradeoff is general memory overhead vs.
cache-able pay-as-you-go overhead.

Best regards
Stefan