in reply to Re^2: Unifying namespaces of @name and $name to simplify dereferencing?
in thread Unifying namespaces of @name and $name to simplify dereferencing?

sub name {
    my $name = shift;
    exists $name{$name} and return $name{$name};

[download]
well obviously you are passing a hash ref in this model because of the curlies {}

No. The name passed in (update: in normal behavior, obviously) is a string, the $name{...} lookup is into a previously defined hash: 

my %name;
my @name;

[download]
</nitpick>

Update: it is in your model where confusion arises about the type of the passed $name.

perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'

Replies are listed 'Best First'.
Re^4: Unifying namespaces of @name and $name to simplify dereferencing?
by LanX (Saint) on Mar 25, 2016 at 19:43 UTC
    > Update: it is in your model where confusion arises about the type of the passed $name.

    yes you are right, $name = shift should do no aliasing automatically, Perl needs universal scalars which are untyped.

    see also my other replies, discussing typed my $name[] = ... declarations to be able to pass/assign references which work without -> operator.

    update

    > No. The name passed in (update: in normal behavior, obviously) is a string, the $name{...} lookup is into a previously defined hash:

    yes and in feature "autoref" this should never compile!

    Because of the alias $name = \%name in the upper scope a redeclaration of a simple scalar $name in the sub would make $name{...} accessing an undefined variable.

    I.o.W. identifiers must be unique in any scope and you would achieve this compile time checking without needing to use Perl Critic.

    Cheers Rolf
    (addicted to the Perl Programming Language and ☆☆☆☆ :)
    Je suis Charlie!

[reply]
[d/l]
[select]

In Section Meditations