In that case, look at it this way: you have your standard unix toolkit. grep, find, sed, sort and so on; and you've added to it a number of new tools. That's fine and your choice to make them seperate is completely reasonable. Now, suppose you were to write a solution for a slightly different task, one that didn't have anything to XML or your current problem set. Would you use /bin/sh? Would you use Perl? In many cases either one makes sense... now you just have to make sure your tools aren't clunky, so you can use them with the same ease as you'd use grep and friends in a shell script. Making it possible to use standard input and output helps -- you can certainly pipe perl scripts with one another.

In reply to Re^3: Chaining scripts smartly by gaal
in thread Chaining scripts smartly by loris

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.