Because it's in one
use call, it's relatively easy to extract--just pull out everything between
use Module::Metadata and the next semicolon, rework it into something a bit safer, and
eval it. Or even better,
reval it. That's the approach the module's
extract_metadata function takes--it constructs a very restrictive
Safe container, massages the code into a call to
Module::Metadata->new, and evalutes it in the
Safe container.
$safe->permit_only(qw(:base_core :base_mem));
$safe->deny(qw(repeat range));
The actual code is a bit more complicated than this, because it handles nesting and (basic) quoting correctly in case a future metadata field accepts a coderef or something, but that's the gist of it. It also responds to use Module::Metadata 1.0 (version numbering) correctly by calling Module::Metadata->VERSION.
By the way, thanks for mentioning interoperability. I should add in a field for operating systems.
=cut
--Brent Dax
There is no sig.
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.