Perl is not C or C++ or Java (no function prototypes/signatures), so you can't really write a plugin for doxygen, at least not a very good one.
Well, you can, given your code conforms to one style, but if you're going to do that, you might as well use
I myself like to use Test::Pod::Coverage to make sure my public apis are documented with good ol pod :)
Actually, I do recall that B::Xref could be very very handy to accomplish something doxyish ...
i think i'll suggest that gmpassos and markov consider employing those in their respective thingamajiggers, maybe :)
|MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"|
|I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).|
|** The third rule of perl club is a statement of fact: pod is sexy.|
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.