...shell out to do something, or do it all in Perl. Many purists argue that if it's possible to do it in Perl, you should do it in Perl. Portability and such.
I am not sure it is possible to argue that one should *generally* use a pure Perl solution, or *generally* shell out.
It's on a case by case basis.
For me, I suppose the deciding factor is portability requirements.
If the code needs to run in many different environments, such as CPAN module, then I would use pure Perl as much as possible. Definitely if it is possible in the core, less likey if a non-core modules is required. The result is probably quicker execution time.
If my production environment is limited to a certain type, as in your specific example, where the environment may be assumed, then I see nothing wrong with using the toolkit.
The result is probably quicker implementation time.
--
bm
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.