Hi! On 11/17/2007 08:42 AM Sebastian Bergmann wrote: > Stefan Marr schrieb:
>> And there has been a discussion to include another Interface definition in >> between the reflection classes and the underlying infrastructure, to be able >> to use a parser and handle Reflection without loading the classes. But don't >> know how that much about this idea. Falko? > Yes, Static Reflection (ie. being able to use the Reflection API without > the class being loaded) is something I would really like to see in the > component. I fully agree here. Jakob Westhoff has written something in this direction and AFAIR you already talked to him at FrOSCon about integrating it. I'm CCing Jakob, to see what the status in this direction is. >> Think this was everything about the Reflection Component to be reported. >> Currently, we are investigating some nice new meta programming techniques >> and are playing with the Runkit extension and some core hacks. >> So we thought about other additions to the Reflection classes, like >> getCode/setCode on ezcReflectionMethods, but this would probably not issue >> for a ezcReflection, because it would depend on Runkit. > You want to depend on Runkit for the ExtendedReflection component? That > is crazy :-) Although the idea sounds alluring, a hard dependency on ext/runkit is a big no-no. Beside that, I doubt that any core-hacks are easy to get into PHP. However, an optional usage of ext/runkit (maybe through a tie-in?) sounds like a good thing TM. Regards, Toby -- Mit freundlichen Grüßen / Med vennlig hilsen / With kind regards Tobias Schlitt (GPG: 0xC462BC14) eZ Components Developer [EMAIL PROTECTED] | eZ Systems AS | ez.no -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
