merlyn is right. Personally, while maybe not the most
elegant way to do so, having to include a new
use
statement for each new module has a self-documenting
quality to it. But it is indeed error prone.
What you could do is scan a particular directory for .pm
files in a BEGIN block like so:
use strict;
use Data::Dumper;
BEGIN {
# scan the current directory
eval{require $_} for <*.pm>;
};
my @class = (
Foo->new,
Bar->new,
Baz->new,
);
print Dumper $_ for @class;
This works (assuming that the corresponding modules
exist and are free of compilation errors)
, but without precautions it will really be
more error prone than just using the modules explicitly.
Neat stuff though .... Perl rules! :)
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
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.