I am working with a code written in at least three different languages. Two of these are parsed quite well by the inline documentaition/call-graph engine called doxygen (which seems to parse c-like code fairly well). I'd like to use doxygen for the perl components too, so all my docs can be managed in a single place.

Natively, the perl code isn't parsed well but I think with some serious munging the perl code could be made to look more c-like. The temporary, munged file would not have to actually be functional, just look like it to a c parser.

Has anyone already solved this problem in another context?

I'm sure the authors of doxygen would love to include a solution as a new helper. (hint hint) I'd love to take a crack at it, but it may be some time before I will be able to work on it.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.