For instance the filepath could be taken to make a distinction between trusted and new code.

How does that help? Three of the four examples I gave still stand, and you still can't syntax check a module.

And rurban's suggestion to wrap the code into a Safe environment

Safe is considered not safe.

Tell me, PPI can find BEGIN-Blocks like in ''=~('(?{B'.'EGIN{print "owned"}})') ?

It shows as a regex literal, which sounds good to me.

So wouldn't be of much help when searching for evil code, since attackers could use these limitations.

Using PPI removes the need to detect such attacks. The only reason you need to detect the attacks is that your method is susceptible to them.

In reply to Re^3: Intercepting compile time blocks like BEGIN {} by ikegami
in thread Intercepting compile time blocks like BEGIN {} by LanX

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.