Re^4: referances of hashes, and subroutines

It's magical to the extent that prototypeing is generally frowned on so is one of the lesser known corners of Perl.

It is also magical in that the local context doesn't provide enough information to understand that there may be side effects when calling the sub. That is dangerous magic. Passing a reference to a sub explicitely is a strong hint that the referent will be altered.

DWIM is Perl's answer to Gödel

Comment on Re^4: referances of hashes, and subroutines

Replies are listed 'Best First'.
Re^5: referances of hashes, and subroutines by ff (Hermit) on Apr 23, 2006 at 01:05 UTC
And by the way, it's nice to do a favor for yourself within the subroutine that's receiving the reference to name the variable with a little suffix that implies that the scalar variable is not just a number or a string but that it is a REFERENCE flavor of scalar! e.g. `use strict; my %hash = qw( abc xyz ); print "Hash key(s) are:\n"; print "$_\n" foreach my_sub( \%hash ); sub my_sub { my ( $hash_hr ) = @_; return ( keys %$hash_hr ); }` [download] In this case, since passing a hash reference, my suffix is 'hr'. If it was an array reference, I'd tack on '_ar'. The suffix does nothing to guarantee that what's in that scalar variable is really an array reference or a hash reference, but it sure makes reading over the code later easier when you are trying to remember what each variable is supposed to be doing and how it is built. By the way, even though only one argument is being passed, I like my subroutines to receive them from @_ via list context since it makes it easier to grow/evolve the subroutine later on. Same for passing return values....	[reply] [d/l]

Replies are listed 'Best First'.

Re^5: referances of hashes, and subroutines
by ff (Hermit) on Apr 23, 2006 at 01:05 UTC

use strict;
my %hash = qw( abc xyz );
print "Hash key(s) are:\n";
print "$_\n" foreach my_sub( \%hash );

sub my_sub {
    my ( $hash_hr ) = @_;
    return ( keys %$hash_hr );
}
[download]

By the way, even though only one argument is being passed, I like my subroutines to receive them from @_ via list context since it makes it easier to grow/evolve the subroutine later on. Same for passing return values....

[reply]
[d/l]