Re: passing arguments in a dispatch table

Looks OK to me, although I don't really know what you're testing. %$dispatch is indeed a hash of CODE-refs, which you can use a "dispatch table." But you knew that. What was the question again?

-sam

Comment on Re: passing arguments in a dispatch table

Replies are listed 'Best First'.
Re: Re: passing arguments in a dispatch table by CharlesClarkson (Curate) on Apr 28, 2002 at 06:36 UTC
Gee. You'd think you weren't looking over my shoulder the whole day and only had this one message to figure out what was going on. :) If we change the dispatch table: `my $dispatch = { add => \&add_entry( $fruit ), };` [download] We get this result: Sun Apr 28 01:23:38 2002 <-- in sub Sun Apr 28 01:23:39 2002 Not a CODE reference at aaaa.pl line 17. The test in the original example allowed me to see that the times were in the correct order. If perl was running the sub immediately, the times would be out of order. I was unsure if this test made sense. Hence the question. HTH, Charles K. Clarkson Clarkson Energy Homes, Inc.	[reply] [d/l]

Replies are listed 'Best First'.

Re: Re: passing arguments in a dispatch table
by CharlesClarkson (Curate) on Apr 28, 2002 at 06:36 UTC

Gee. You'd think you weren't looking over my shoulder the whole day and only had this one message to figure out what was going on. :)

my $dispatch = {
    add => \&add_entry( $fruit ),
};
[download]

Sun Apr 28 01:23:38 2002 <--   in sub 
Sun Apr 28 01:23:39 2002
Not a CODE reference at aaaa.pl line 17.

The test in the original example allowed me to see that the times were in the correct order. If perl was running the sub immediately, the times would be out of order. I was unsure if this test made sense. Hence the question.

[reply]
[d/l]