Re: Your named arguments

in reply to Your named arguments

At work we use Params::Check. Reasonable simple, and it does the job. The example in the documentation uses %hash, which I don't approve of. I use %args_in which covers the meaning nicely. Maybe %params_in would be even better.

Arjen

All that is gold does not glitter...

Comment on Re: Your named arguments Select or Download Code

Replies are listed 'Best First'.
Re^2: Your named arguments by Juerd (Abbot) on Nov 09, 2005 at 21:02 UTC
I use %args_in which covers the meaning nicely. Maybe %params_in would be even better. No, parameters are expected, while arguments are passed. The hash contains arguments, never parameters. Given `foo => $bar`, the parameter is "foo", and the argument is $bar, named by the name of the parameter. In Perl 6: `sub foo ($foo, $bar) { # $foo and $bar are parameters # But in the sub itself, they represent the arguments ... } foo(42, 15); # positional arguments foo(foo => 42, bar => 15); # named arguments foo(bar => 15, foo => 42); # same thing :)` [download] Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Your named arguments
by Juerd (Abbot) on Nov 09, 2005 at 21:02 UTC

I use %args_in which covers the meaning nicely. Maybe %params_in would be even better.

No, parameters are expected, while arguments are passed. The hash contains arguments, never parameters.

Given foo => $bar, the parameter is "foo", and the argument is $bar, named by the name of the parameter.

In Perl 6:

sub foo ($foo, $bar) {   # $foo and $bar are *parameters*
    # But in the sub itself, they represent the *arguments*
    ...
}

foo(42, 15);                # positional arguments
foo(foo => 42, bar => 15);  # named arguments
foo(bar => 15, foo => 42);  # same thing :)
[download]

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

[reply]
[d/l]

In Section Meditations