In your case, I would second the advice to open all the output files up front and write to whichever is appropriate
with the caveat that you try not to recompile the regex for each possibility (i.e. store the regexen as qr// objects).
In the case of larger numbers of output files, I would create a structure something like:
@natures = [{ filename => "h.ll",
criterion => qr/blasphemer/,
handle => undef # this line not actually needed
},
...
and open each handle as needed, with a loop at the end
over natures to close them all.
Hey, wait, you could even have some kind of object encapsulating that hash, and let an object method do the
match. But that starts to sound like Mail::ListDelivery/
Mail::Audit::List.
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.