Check out PPI, it's apparently a framework for parsing perl (eek! i haven't reviewed it yet).

I know people always say, don't parse perl, but in this case, it wouldn't be so bad. Since a BEGIN block can only look like sub BEGIN {} or BEGIN{}, i suggest you programatically change the BEGIN block to something like IwannaBEGINevil. Off the top of my head something like s/\bBEGIN\b/IwannaBEGINevil/ will do (no real thought put into the regex).

Then you can audit that sub like you would any other user defined sub (if you can do that).

Oy!

MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
** The Third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: Auditing BEGIN blocks? by PodMaster
in thread Auditing BEGIN blocks? by diotalevi

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.