|Pliant talk forum
Discussion: Highlight Code Execution Paths
Rather than syntax highlighting that is not too usefull,
emphasize important code execution paths.
|Message posted by maybe Boris Reitman on 2008/10/24 02:08:44
|Can we bring the tag-cloud concept from web2 websites to software analysis ?
Can we make the code lines that are important fat and those that are details thin ?
If we think of code executing paths as arteries of blood,
can we identify the fat ones ?
This would be a cool feature for a programming editor.
Can we use profiling data to obtain the information needed to make it happen ?
Can we identify some key execution points manually and then derive execution paths
from a profile dump to connect them ? Can we come up with a metric that will weight
discovered paths ?
For understanding pliant code it would be very usefull.
But also for any other software too.
Then flowchart diagrams could be generated from that data.