Hi Sebastian, thanks for your review. Think Falko has already added some of your markups for the design document to the tex-file. Should be no problem to finish this.
Tobias already told me about his annotation parser, so i'll have look at it. > Out of curiosity: One of the use cases mentioned for the CodeAnalyzer > component is software metrics. Have metrics (such as McCabe, for > instance) already been implemented? I am asking because this is a > topic that is getting more and more important in the PHP world and > several people are working on solutions. Yes, it is already implemented: http://instantsvc.toolslave.net/trac/browser/branches/transition/components/ CodeAnalyzer/src/code_analyzer.php codestats-report.php generates a html report with this basic metrics. Can be found at: http://instantsvc.toolslave.net/trac/browser/branches/transition/components/ CodeTools/src Here we got only very basic metrics, the most important metrics like inner coupling of classes and there methods are not measured at the moment. For measuring advanced metrics we need information about the possible call-graphs. Think Falko has done something in this direction, but to visualise them. Could possibly reused to calculate some metrics from it. But therefore, the reflection api was not enough. It is using a php parser to get those information. Kind Regards Stefan -- Components mailing list [email protected] http://lists.ez.no/mailman/listinfo/components
