That 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 j

That 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.