comment on

I am not familiar with doxygen or javadoc, but Pod is easy enough to convert to HTML.

My guess it that doxygen or javadoc do some sort of static source code analysis as well? Such a thing is hard to do well in perl, as variables and methods can be created dynamically at runtime using eval. The perl profiler has the ability to display the function call tree after a run, which may provide a start in developing a hierarchical search structure.

Update: fixed a typo.

-Mark

In reply to Re: documentation generator? web-enabled perldoc? by kvale
in thread documentation generator? web-enabled perldoc? by geektron

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.


Do you know where your variables are?
	PerlMonks