As a side note, when you see duplicated code, it's time to refactor it. For example, you are prompting for, and reading, the user's responses, but you do this several times in a row. It looks like it's time for a subroutine.

my $fileext 
    = prompt("\nEnter extension of files to look in (example: log or t
+xt):\n");
my $playertofind 
    = prompt("\nEnter exact name of player to find and replace:\n");
my $newplayer
    = prompt("\nEnter exact name of player to replace $playertofind wi
+th:\n");

sub prompt {
    my $message = shift;
    print $message;
    chomp ( my $response = <STDIN> );
    print "\nConfirmed: $response\n\n";
    return $response;
}

[download]

Remember: no duplicate code :)

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

In reply to Re: Simple file editing problems2 by Ovid
in thread Simple file editing problems2 by alpal

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.