If you're going for the minimum in terseness; you can always use a temporary file:

./print_list >/temp/temp.txt; perl filter.pl temp.txt file.txt; rm temp.txt

filter.pl would read from the first file, then use the contents to substitute in the second file:

use strict;
use warnings;

open(my $file1, '<', $ARGV[0]) or die "Can't open $ARGV[0]: $!\n";
my @substitutions = <$file1>;
close($file1);
chomp(@substitutions);

open(my $file2, '<', $ARGV[1]) or die "Can't open $ARGV[1]: $!\n";
while(my $line = <$file2>) {
  for my $replace (@substitutions) {
    next unless $replace;  # skip blanks
    $line =~ s/\Q$replace\E/foo/g;
  }
  print $line;
}
close($file2);

[download]

In reply to Re: How to handle both a STDIN pipe and file from command line? by ramlight
in thread How to handle both a STDIN pipe and file from command line? by keithw99

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.