I think that /g could prevent the recursion problem, so i have two way that would work :
# version 1
## problem, does not skip comments
undef($/);
my $text = <fp>;
foreach my $pat (keys %my_replacement) {
    $text =~ s/$pay/$my_replacement{$pat}/g;
}
print $text;

[download]
... and ... 
while (<fp>) {
    if (!m/^\s*\/\//) {
        # skip comments
        next;
    }
    $text .= $_;
}

foreach my $pat (keys %my_replacement) {
    $text =~ s/$pay/$my_replacement{$pat}/g;
}
print $text;

[download]
may the foo be with you

In reply to Re: Read In A File, Manipulate It, Spit It Back Out by MZSanford
in thread Read In A File, Manipulate It, Spit It Back Out by JojoLinkyBob

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.