You can find the line without splitting first:
chomp @file;
my @matches = grep { $file[$_] =~ /^\Q$storeline|\E/ } 0..$#file;
no_match($storeline), return unless @matches;
duped_ids($storeline), return if @matches > 1;
my ($number, $image, $name, $text, $used) = split /\|/, $file[$matches
+[0]];
# do what you do modifying those vars
$file[$matches[0]] = join '|', $number, $image, $name, $text, $used;
rename '/path/to/info/smileset.txt', '/path/to/info/smileset.bak' or d
+ie $!;
open FLE, '>', '/path/to/info/smileset.txt' or die $!;
print FLE $_, $/ for @file;
close FLE or die $!;
The
&no_match and
&duped_ids subs are up to you, they would probably log the error.
After Compline,
Zaxo
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.