Since the discussion is becoming one of style preferenece, I'll add mine. Dispatch tables are often a suprise to someone reading through code. It's common for there to be only one in a module, if that, so it's good to call the reader's attention to what's going on.
While I might use
$op_map{$op_choice}->(@args);
for a one-off, or where I was using it a lot, for most code I'd do something along the lines of
naikonta's later suggestion, only with some correspondence between the names, as in
my $op = $op_map{$op_choice};
$op->(@args);
This separates the lookup from the invocation, so the invocation is easier to see. It also makes adding a default function easier, as
naikonta already showed.
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.