I have a Perl program that processes Perl source and generates fake C++ headers that doxygen will process. Doxygen doesn't have a hook for adding a new parser, so this is the only way to hack it. The doxygen way of doing things depends pretty heavily on special comments. My doxygen hack pulls a lot of stuff automatically _without_ special comments, but is highly dependent on my coding style. I can only recommend it as an example, it's not like supported or anything.
Having said all that, I am in fact a fan of doxygen. I find it in use all the time on various open source projects. mma > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 15, 2003 5:30 PM > To: [EMAIL PROTECTED] > Subject: pretty pictures > > > I was playing with doxygen (www.stack.nl/~dimitri/doxygen/index.html) > (think javadoc for C++) and thought I'd pass along some random pictures. > > Doxygen unfortunately doesn't handle perl code, and even has problems > with parrot's C. (IMHO, the world needs a wrapper hack which allows > you to run all these variously broken code analysis tools, and then gloms > their outputs together into something browsable. Ah well. Todo list.) > > Attached are the interpreter.h include tree, and the PMC and Arena > datastructure graphs. (Why not Interp? See previous paragraph). > > GraphVis (www.graphviz.org) did the actual drawing. > > Hmm. Maybe a picture of the complete include graph would be useful > introductory material... > > Mitchell >
