How often would this profiling have to happen? Seems to me that if it's a "once per build" or "once per someone pressing the button", then go for the more expensive analysis checking through the files. Just build up a tree that shows which classes implement what or inherit from where, save that along with file modification times, and if you have to redo the analysis (on a running system, for instance) then just check files that have changed since last check. It'll likely be expensive once, but probably not very much (after all, you only care about class, you don't need to parse docblocks or anything like it).
regards Peter -- <hype> WWW: plphp.dk / plind.dk LinkedIn: plind BeWelcome/Couchsurfing: Fake51 Twitter: kafe15 </hype> -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php