>>What is the initial requirement anyhow?
I need to chart a map :) For better orienting in that horror code when a new programmer comes or when committing a dumb patch that crashes a system. In this time we cannot afford to cover all the code with units and searching for a magic-tool to handle a bit that ancient horror:) Sadly, it is idea of PMs - but work is work:)
--
For now - the only decision i have - is a bad-percentage analyzer built on regexes, they firstly remove some part of 'garbage' (use, require, vars, qq[] constructs etc) from code and suppose that remaining shit is a pool of sub calls. Of course it is a really bad solution - considering that sub-calls may be built dynamically, etc.
Now i'm examining the Devel::Call* section of CPAN - maybe, i can recieve some kind stack of subcalls with -d param..:)
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.