Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What does `sub bar { +{$_[1] => $_[2]} }` exactly do?

Tags:

hash

perl

I don't understand the + sugar sign in this example taken somewhere while goggling:

sub bar { +{$_[1] => $_[2]} }

I wrote this and I don't see any differences here:

use Data::Dumper;

# Not any differences here
my $foo =  {value => 55};
my $bar = +{value => 55};

print Dumper $foo;
print Dumper $bar;

# Oh ! Here there is something...
sub foo {  {$_[1] => $_[2]} };
sub bar { +{$_[1] => $_[2]} };

print Dumper foo('value', 55);    
print Dumper bar('value', 55);    

foo returns

$VAR1 = 55;
$VAR2 = undef;

bar returns

$VAR1 = {
          '55' => undef
        };
like image 487
nowox Avatar asked Jul 03 '15 07:07

nowox


People also ask

What do u mean by bar?

a place where drinks, especially alcoholic drinks, are sold and drunk, or the area in such a place where the person serving the drinks stands: They noticed him going into the hotel bar.

How do you use the word bar?

In British English, bar can be used as a preposition after words such as all, every and any to mean 'except', as in 'The city centre is closed to all traffic after 6pm bar buses and taxis'.

What does it mean to bar someone?

LAW. to prevent something or someone from doing something or going somewhere, or to refuse to allow something: bar sb/sth from (doing) sth Lawyers on both sides have been barred from discussing the case in the press.

Will not bar meaning?

to refuse to accept or have anything to do with something: Karen called her mother and asked her to come and stay, but Mum wouldn't have a bar of it. She wants reform but voters are not having a bar of it.


1 Answers

It helps the parser to distinguish between an anonymous hash and a code block.

Citing Learning Perl Objects, References & Modules

because blocks and anonymous hash constructors both use curly braces in roughly the same places in the syntax tree, the compiler has to make ad hoc determinations about which of the two you mean. If the compiler ever decides incorrectly, you might need to provide a hint to get what you want. To show the compiler that you want an anonymous hash constructor, put a plus sign before the opening curly brace: +{ ... }. To be sure to get a block of code, just put a semicolon (representing an empty statement) at the beginning of the block: {; ... }.

Or from the documentation on the map function:

"{" starts both hash references and blocks, so "map { ..." could
be either the start of map BLOCK LIST or map EXPR, LIST. Because
Perl doesn't look ahead for the closing "}" it has to take a guess
at which it's dealing with based on what it finds just after the
"{". Usually it gets it right, but if it doesn't it won't realize
something is wrong until it gets to the "}" and encounters the
missing (or unexpected) comma. The syntax error will be reported
close to the "}", but you'll need to change something near the "{"
such as using a unary "+" or semicolon to give Perl some help:

    %hash = map {  "\L$_" => 1  } @array # perl guesses EXPR. wrong
    %hash = map { +"\L$_" => 1  } @array # perl guesses BLOCK. right
    %hash = map {; "\L$_" => 1  } @array # this also works
    %hash = map { ("\L$_" => 1) } @array # as does this
    %hash = map {  lc($_) => 1  } @array # and this.
    %hash = map +( lc($_) => 1 ), @array # this is EXPR and works!

    %hash = map  ( lc($_), 1 ),   @array # evaluates to (1, @array)

or to force an anon hash constructor use "+{":

    @hashes = map +{ lc($_) => 1 }, @array # EXPR, so needs
                                           # comma at end

to get a list of anonymous hashes each with only one entry apiece.
like image 131
Matteo Avatar answered Oct 21 '22 06:10

Matteo