comment on

This is very cool, particularly for such a short program. I like dot a lot. It is a very powerful graphing engine.

The problem of this script is, of course, that not everyone uses the & convention for calling subroutines. One thing that comes to mind is flag "x" (1024) for the -D option to perl, which does a syntax tree dump. I have never seen its output, and I don't have perl compiled with -DDEBUGGING, but I wonder it that could be used to generate a more complete call tree.

The other option would be to run the script with "perl -d:DProf" (using the Devel::DProf module) and then use the call graph generated by dprofpp to generate the dot output. In this case, however, only the subroutines that got called during the execution are graphed.

Very interesting problem, in any case.

--ZZamboni

In reply to RE: Generate a Graph-ical call tree for your *.pm perl modules by ZZamboni
in thread Generate a Graph-ical call tree for your *.pm perl modules by trony

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.


laziness, impatience, and hubris
	PerlMonks