Data-driven approaches FTW!

Though I'd be tempted to do things a bit more perlishly (at least for my own definition of perlish): 

my @matchers = (
  [ qr/(Lz0|PLATO)/i => 'Apps' ],
  ...
);
for my $check (@matchers) {
  if ($release_name =~ $check->[0]) {
    $category = $check->[1];
    print "[INFO] Category: $category\n";
    last;
  }
}

[download]
Actually, a bit more perlish, IMO, would be to replace that for loop altogether: 
use List::Util qw(first);
my $category = map {
  $_ ? $_->[1] : undef;
} first {
  $release_name =~ $_->[0];
} @matchers;
if ($category)
{
  print "[INFO] Category: $category\n";
}
else
{
  print "[ERROR] Unrecognised release type: $release_name\n";
}

[download]
But maybe that's just me. :-)

In reply to Re^2: if,if and again,if by Tanktalus
in thread if,if and again,if by cesapun

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.