Re^2: shift implicit dereference

[tobyink]

Another place a unary plus is often useful is to protect against the effects of the fat comma:

use constant MONIKER => 'name';

my %hash1 = ( +MONIKER => 'Monica' );  # compared with...
my %hash2 = (  MONIKER => 'Monica' );

use Data::Dumper;
print Dumper(\%hash1, \%hash2);

[kcott]

I get the same results as Sören. I'm using v5.18.1 (darwin-thread-multi-2level).

(MONIKER() => 'Monica') produces 'name' => 'Monica' in the Dumper output.

[LanX]

or maybe putting in parens is more obvious?

  DB<117> use constant MONIKER =>"name"

  DB<118> %hash1 = ( (MONIKER) => 'Monica' ); 
 => ("name", "Monica")

  DB<119> $hash1{ (MONIKER) }
 => "Monica"

  DB<142> [map { my $y = uc; ({$y => 1}) } "a".."c"]
 => [{ A => 1 }, { B => 1 }, { C => 1 }]

  DB<143> print ((1==0) ? "true" : "false")
 => 1
false
  DB<144> sub tst { ${ (shift) } }

  DB<145> tst \"a"
 => "a"

[Happy-the-monk]

That's looking very nice but...

$VAR1 = {
          'MONIKER' => 'Monica'
        };
$VAR2 = {
          'MONIKER' => 'Monica'
        };

$ perl -v

This is perl 5, version 14, subversion 2 (v5.14.2) built for i686-linu
+x-gnu-thread-multi-64int
...

Cheers, Sören

[boftx]

Confirmed, same result with 5.10.1 on my shared hosting account.

$ ./monktest.pl
$VAR1 = {
          'MONIKER' => 'Monica'
        };
$VAR2 = {
          'MONIKER' => 'Monica'
        };

$ perl -v

This is perl, v5.10.1 (*) built for x86_64-linux-thread-multi