doxygen parses sourcecode to determine constants, function signatures, etc.. function signature won't work for perl (as i'm sure you realize).

doxygen includes hyperlinked syntaxt hilighted sourcecode in its output, and there is no reason you couldn't do that with perl other than its of little use most of the time (and parsing perl is hard).

doxygen links all function references to the function documentation, and there's no reason a pod translator couldn't do that (in fact Pod::Html tries to resolve those when possible).

Anyway, here is something other than just pod:

• ePod - write easy and simple in easy-POD, convert to POD, and from there you know the way.
• OODoc

Anyway, perl's only issue with pod (besides the fact that L<blah blah|http://some.url/> isn't legal yet), is that there aren't many tools (like doxygen) to generate pod from raw source (as much is possible) for module writers (module users shouldn't need to deal with such tools).

BTW - I like pod :)

---

---

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