From: Falko M. <ma...@fa...> - 2009-07-21 21:48:26
|
> phpcallgraph does a lexical investigation (sequential as appears in > the source file) of the methods in a class. This does not do a > traversal according to how the methods are called. > > It does hold an overview of the relationships after it has finished > (but doesn't know what's beyond the next layer during the > startFunction() and endFunction). During destruct, its seen > everything. We know it knows because it passes all these > relationships to dot. > > So, during destruct it would be possible to ask for a tree of > depended-upon methods for a given method. It would be possible to > visit each entry point method and to get all "dependent routines" that > need to be shown. > > A question would be to what depth of dependents we would want to show. I would suggest to have a numeric option for that. > Does my logic make sense? Yes, it does. However, drivers are supposed to support multiple analyses on different file sets, with reset being called after each analysis. Using the destructor would only allow to get the data of last pass, but maybe that's ok, for the beginning, since the umlgraph driver is working differently anyway. |