You do have code for these cases? So in addition to your logic above you have: 
sub this {
  return "this"; # Whatever
}

sub that {
  return "that"; # Being simple here
}
# etc

[download]
Combine the two: 
my %action = (
  this => sub {return "this"},
  that => sub {return "that"},
  # etc
);

# Then later:
if (exists $action{$in}) {
  $action{in}->();
}

[download]
In fact if you have a lot of cases you can probably find room to factor: 
sub ret_simple_returner {
  my $arg = shift;
  return ($arg, sub {$arg});
}

my %action = map ret_simple_returner($_), qw(this that);

[download]
The point being that every time you eliminate the need to keep two pieces of code in sync you eliminate another possible source of bugs...

In reply to Re (tilly) 1: use slack; by tilly
in thread use slack; by epoptai

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.