Currying closures might be useful here, but that depends on when you are building the dispatch table if I understand your problem correctly. If you don't mind wasting efficiency, you might want to lift out common arguments to the subs (if any exist) to the dispatch call site and build the dispatch table like this during each iteration of the while loop:

my %dispatcher = ( 
  foo => compute_interval($titi), 
  bar => compute_interstice($tata), 
  baz => compute_inact_and_expo_effective($toto),
  qux => get_exposure_service($bling)
);

$dispatcher{$action}->(<insert_common_args_here>) if exists($dispatche
+r{$action});

sub compute_interval {
   my $args = shift;
   return sub {
      # do something useful with args here..
   }
}

sub compute_interstice {
   my $args = shift;
   return sub {
      # and so on
   }
}
[download]

I'm sure there's a better way to do this that my idiocy is incapable of figuring out right now too.
There are lots of better resources regarding how to use closures available -- try searching for the word 'closures' on this site for more info.

Anonymous Lee

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.