On Thu, 2011-01-06 at 14:38 +0100, Stefan Marr wrote:
>
> On of those things is that you actually use ReflectionClass to reflect
> on a trait.
> That is really an implementation detail, and should be changed to not
> confuse anyone on a conceptional level. We should not expose that kind
> of engine/implementation detail.
This is the same with interfaces. What does class_exists('some_trait')
do? - I assume that returns true too.
> Thus, there remains stuff to be done about reflection. In general, I
> would like to be able to access all information that was in the source
> code. However, time constraints are an issue for me. If there would be
> a new release date for an alpha or something, I think I could get some
> time to work on it...
I hoped to do some work on it over Christmas vacation, too, but did
other stuff in the end ...
johannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
