to see how it has been written and learn from it?

That is a bit like learning by osmosis, its easier to learn by reading a book

Devel::Graph

xref graph site:perlmonks.org
sub_graph.pl: perl call graph generator
Generate a Graph-ical call tree for your *.pm perl modules
Perl diagram/chart generator
Analyzing large Perl code base.
Documenting Perl Scripts
Auto documentation
Becoming familiar with a too-big codebase?
http://drdobbs.com/architecture-and-design/184404560# Creating Perl Code Graphs | Dr Dobb's
Devel::GraphVizProf
graphvizprof site:perlmonks.org
Reverse Engineering Perl Tool?
Project Management: Graph & Diagram for Visualizing & Analyzing Structure with GraphViz
GraphViz::ISA


In reply to Re: Visualizing the skeleton of a perl code by Anonymous Monk
in thread Visualizing the skeleton of a perl code by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.