Beefy Boxes and Bandwidth Generously Provided by pair Networks
We don't bite newbies here... much

Re^4: Use method/function signatures with Perl

by ihb (Deacon)
on Dec 08, 2004 at 16:02 UTC ( #413242=note: print w/replies, xml ) Need Help??

in reply to Re^3: Use method/function signatures with Perl
in thread Use method/function signatures with Perl

If I cannot pass the foo parameter in (to be silently ignored if necessary), that's a sign of bad assumptions.

Your assumption that subroutines silently ignore unknown arguments is the bad assumption. Nothing says this is the rule.

If it's for forwards- or backwards-compatibility then it's not unknown extra arguments. They're there for a reason and the module author is aware of this. Future problems won't arise for you adding those arguments. For my issues with this, see Re^2: Use method/function signatures with Perl.

As for dispatches (like your example with rendering engines), you can take care of this with very little code changes. In your dispatch table (if you have one -- otherwise create one) add which parameters that should be passed (or which shouldn't be passsed, or whichever way suits your problem) and then pass just those parameters. This is trivial to implement for someone like you. For example, a simple draft to illustrate my solution code-wise can look like

sub foo { print "foo: @_\n" } sub bar { print "bar: @_\n" } sub safe_dispatch { my ($dispatch, $name, $params) = @_; my ($code, @keys) = @{$dispatch->{$name}}; my @params = map { $_ => $params->{$_} } grep { exists $params->{$_} } @keys; return $code->(@params); } my %dispatch = ( foo => [ \&foo, qw/ foo common / ], bar => [ \&bar, qw/ bar common / ], ); my %params = ( foo => 1, bar => 1, common => 1, ); safe_dispatch(\%dispatch, $_, \%params) for qw/ foo bar /; __END__ foo: foo 1 common 1 bar: bar 1 common 1
All I've changed from a trivial dispatch is added parameter names in the dispatch table, and use a subroutine instead of $dispatch{$name}->(%params) which typically would be used.

This approach could easily be tweaked for most other situations and similar problems. I admit there might be cases where this could be cumbersome but for typical use I think it's trivial to get around your problem.

A little code with a great benefit, the way I see it. (See Re^2: Use method/function signatures with Perl for the benefit.)


See perltoc if you don't know which perldoc to read!
Read argumentation in its context!

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://413242]
Corion waves to virtualsue
[virtualsue]: I have made a post for the first time in ... years
[marto]: hey virtualsue!
Eily thought about Neko Case first, something might be wrong with my brain's wiring
[virtualsue]: I recommended dbic-migration even though I am having trouble with it this week. It might be my fault.
[ambrus]: wow! I haven't seen you here for a long time, virtualsue
virtualsue waves back
[Eily]: it would have been 2 years in 2 weeks actually. And welcome back virtualsue :)
[Corion]: I think I saw virtualsue more recently in person than online :-D
[virtualsue]: It's true that there was a bigger gap between the 2 yr old post and the one before it

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (15)
As of 2017-09-26 13:47 GMT
Find Nodes?
    Voting Booth?
    During the recent solar eclipse, I:

    Results (295 votes). Check out past polls.