I’ve started to draw up (by hand) some UML diagrams of parts of the cluster code – I figure this way I can better learn (and remember) what belongs to what and what has what.

This really useful where the question comes up of “I need a NdbMgmHandle.. now where are we storing one of those?”

In the past, cscope has been a hell of a useful tool for all this – but it seems to fall down on C++… at least through the emacs mode i’m so fond of. There was also a similar in house tool at SGI which I was incredibly fond of (I don’t think a single day went by where I didn’t use it) – maybe I’ll have to bug people to release it as open source :)

I was thinking a nice perl script could produce some Dia XML (for a bit of by-hand processing i guess). Just chuck it a bunch of header files (with the class definitions in them) and it can sort out a graph of what has what etc.

Maybe Dia XML could be a bit complex for the first go – but hey, even some kind of web thingy could be useful.

I want a quick-glance image, not a pour through everything or grep.

Although I do wish cscope was a bit less broken – it can really get royally confused on some (quite valid) source.