Perl really needs more tools to support software engineering. First and foremost among those is allowing metrics to be gathered. (Yes, there are bad metrics and there are metrics that can be easily weaseled, but I'm not telling you which metrics to use!) Obviously parsing the raw perl isn't going to be easy enough in perl5. But once perl parses it couldn't we navigate the op tree? That should make it easy to see how many non-local variables are affected and what-not.
If somebody has enough free time to put something into a project like this, let me know. Particularly if you're familiar with the way the B:: modules work.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||