3 ms·
CFlow does what you want: http://www.gnu.org/software/cflow/ http://www.gnu.org/software/cflow/ It's primitive compared to the stuff you find in with more ref
by mahmud 17y ago
CFlow does what you want:
http://www.gnu.org/software/cflow/ http://www.gnu.org/software/cflow/
It's primitive compared to the stuff you find in with more reflective languages, at least Common Lisp and Smalltalk, or for that matter binary analysis utilities like IDAPro.
But, theoretically, you could do that only with C-like languages and binary executables: i.e. languages that have a "program entry point".
- DenisM 17y agoThat looks like control flow, not a dependency diagram. Control flow is too complicated for my purposes - I only want to see compile-time dependencies, really just visualization of #include directives would be perfectly fine. Suppose class A comes with callback interface AC. Class B calls into class A and also implements AC, so that A can call it back if needed. In the dependency diagram I want to see dependency from B to A, but no dependency from A to B. The reasn is that A can be understood in isolation without B, but B can not be understod without A. I think compile-time dependency makes for a pretty good proxy of this "understanding" thing.