CharlesClarkson,

I think that you are looking at a closure. As such, data are available as lexicals in the context in which your anonymous sub is defined. Usually you will want $fruit to go out of scope deliberately.

Also, add_entry does nothing with its argument, hence you would not be able to observe a difference:

Warning: untested code 

#!/usr/bin/perl -w
use strict;
$|++;

my $dispatch;
{
    my $fruit = [ qw|apple orange pear| ];
    $dispatch = {
        add => sub { return add_entry( $fruit ) },
    };
}

print scalar localtime, "\n";
sleep 1;
print &{ $dispatch->{add} }, " <-- from sub \n";;
sleep 1;
print scalar localtime, "\n";

sub add_entry{
    print scalar localtime, "$_[0] <--   in sub \n";
    sleep 1;
    return scalar localtime;
}

__END__

[download]

In reply to Re: passing arguments in a dispatch table by rinceWind
in thread passing arguments in a dispatch table by CharlesClarkson

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.