This is a nifty idea -- though I think jeffa's comment is dead-on. The only other point, not a major one: if the input list is long and you're going to execute some shell command on lots of items in rapid succession, you might save some overhead this way:

open( SH, "| /bin/sh" );
...
sub execute {
  my ($com, $columns) = @_;
  # substitute the value from the appropriate column for \0, \1, etc.
  $com =~ s/\\(\d+)\;?/$columns->[$1]/g;
  print SH "$com\n";
}
[download]

This can make a difference when the command line being run involves shell metacharacters (e.g. pipes, redirection, logic operators, etc), because when you pass something like that to "system()", it invokes a new shell to run it. For simpler command lines, printing to SH simply means that perl doesn't do "fork;execvp" (which is what the shell would do anyway, I suppose). For a demonstration, look at (my shameless plug for) shloop -- execute shell command on a list.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.