Hi

One cheesy thing that you could do is to use Doxygen by putting all the Doxygen comments after an __END__.

#-- Perl script

print "Test Perl Script\n";

__END__

/*! \class Test
     \brief A test class.

     A more detailed class description.
 */
[download]

You'd have to use the "Documentation at other places" format and you'd wouldn't get any of the source scanning features.

The other problem is that the .pl extension isn't recognized. You'd either have to work on the Doxygen source, or write a wrapper script that linked your .pm files to a recognized extension. This hack creates problems in the doc itself, because it says things like

  was generated from the following file:

    * test2.cpp
[download]

   * test2.pm
[download]

Also, based on some of the other posts, it appears there is a Perl-to-Doxygen script call DoxyFilt. However, I couldn't connect to that site. It appears to read the POD and parse the module to create pseudo-C files with the Doxygen comments.