On the one hand, I would like better graphical code
analysis tools. On the other hand, I would
like to mention a different kind of code analysis.
A "Return on Investment" (ROI) philosophy would
analyze the code by how much it costs to change the code.
To do this, you can add up all the costs.
Th
Steven W. Orr a écrit :
> Lots of code, calls to, calls by, inheritance, multiple tasks, etc.
>
> What do people use to figure out what's happening?
>
> TIA
>
I've collected some links over time:
http://www.limsi.fr/Individu/pointal/python.html#liens-metaprog
You may look at
# depgraph - graph
On Wednesday, May 2nd 2007 at 12:48 +0200, quoth Daniel Nogradi:
=>> Lots of code, calls to, calls by, inheritance, multiple tasks, etc.
=>>
=>> What do people use to figure out what's happening?
=>
=>This is a pretty cool project just for that:
=>
=>http://codeinvestigator.googlepages.com/codeinv
> Lots of code, calls to, calls by, inheritance, multiple tasks, etc.
>
> What do people use to figure out what's happening?
This is a pretty cool project just for that:
http://codeinvestigator.googlepages.com/codeinvestigator
HTH,
Daniel
--
http://mail.python.org/mailman/listinfo/python-list
Lots of code, calls to, calls by, inheritance, multiple tasks, etc.
What do people use to figure out what's happening?
TIA
--
Time flies like the wind. Fruit flies like a banana. Stranger things have .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black
