I was recently tasked with 'porting' a large body of code from Perl 5.6 to 5.8.x. The following construct (simplified), which was legal in 5.6 is no longer so:

my %$h = ('name' => 'value', ...); ... print $h->{'name'};
I suspect the original author of the sin of cut-and-paste and not understanding references, and hash ref initializers. I changed the code to:
my %h = ('name' => 'value', ...); ... print $h{'name'};
and all is well now. But when explaining this to the group, I couldn't answer the question of whether my change was any better than:
my $h = {'name' => 'value', ...}; ... print $h->{'name'};
So my question is whether anyone has a good reason to choose one over the other? My assumption is that there is no difference.



pbeckingham - typist, perishable vertebrate.

In reply to Relative Merits of References by pbeckingham

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.