Multiple-arg system() doesn't quite work like that (read this). Redirection using the shell metacharacter ">" is handled by the shell, which reads the entire string "program $ref_file > $outfile", parses it, and executes the command with redirection.

When you do multiple-arg system, you're going raw and skipping the shell (usually). Redirections have to be performed manually and you'll lose some convenience you get with using a shell. Example:

sub executeComm {
    my ($outfile, @comm) = @_;

    print "cmd: <", join("> <" => @comm), ">\n";

    # manual redirection - dup(2) STDOUT first
    open(my $ORIGSTDOUT, ">&" . fileno(*STDOUT)) or die $!;
    open(*STDOUT, ">", $outfile) or die $!;

    # run it!
    my $exit = system @comm;

    # restore STDOUT
    open(*STDOUT, ">&=" . fileno($ORIGSTDOUT)) or die $!;

    print "exit: ", $exit, "\n";
}

print "before\n";
executeComm($outfile, $program, $ref_file);
print "after\n";
[download]

If you really want a quick-and-dirty fix for your "whitespace-in-filename" problem, place single-quotes around the filenames, as in:

executeComm ("program '$ref_file' > '$outfile'");
[download]

Now make sure you don't have single-quotes in the filenames...

---

---

• 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.