Your situation made me think back to my early days, facing
the same sort of problem with masses of C code; back then
(before internet connectivity was common), I actually wrote
my own code indexer in C to read a bunch of C source files
and print a simple table that lists the functions defined
in each file, and the subroutines called from within each
function. It really helped.
So, how hard could it be to do that in Perl? Well, not that
hard, if you're willing to be content with less than (but
usually close to) 100% accuracy in the "precision and recall"
measures of subroutine detection.
It's a real bare-bones, quick-and-dirty, not-too-subtle
attempt, but it's here in case you want to try it
out.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.