Presumably, the method which contains the definition of the dispatcher will
be called frequently. Is there any performance related disadvantage to this
for, say, the case that the dispatcher hash is very large?
And if I did want to define the dispatcher as a member in the constructor
along the lines of:
my $self->{message_types} = (
type1 => sub { $self->sub_1(@_); },
type2 => sub { $self->sub_2(@_); },
);
what would the call the dispatcher look like?
I tried:
$self->{message_types}->{$type}->(@args);
but as what I am doing is beyond my understanding of Perl hairiness, I wasn't
suprised to find that it doesn't work. What would the correct code look like?
Thanks,
loris
"It took Loris ten minutes to eat a satsuma . . . twenty minutes to get from one end of his branch to the other . . . and an hour to scratch his bottom. But Slow Loris didn't care. He had a secret . . ."
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.