In your approach, all dispatches have to be integer based (array) where as with a hash, you have the luxury of using any scalar value.

The last bit should be "any string", not "any scalar value".

And in his approach, all dispatches have to be regex-based, and that's rather more luxurious than any constant string.

The cost is in speed. His dispatch takes O(N) to find the correct dispatch, not O(1). 

my $action;

for my $dispatch (@$dispatch_tables) {
    my $regex = $dispatch->{regex};
    if ($input =~ $regex) {
        $action = $dispatch->{action};
        last;
    }
}

die("No match\n") if !$action;
$action->($input);

[download]

In reply to Re^2: Subroutines in Dispatch Tables by ikegami
in thread Subroutines in Dispatch Tables by Anonymous Monk

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.