When defining a normal array or hash, always use (). That's given, and hopefully easiest to remember since it's used the most.

To remember the braces for references, I use this logic: 

# to access a member of an ARRAY, use []
$array[0] = "hello";
# so to define an anonymous array reference, use [] as well
$array_ref = [ "Hello", "World" ];

# to access a member of a HASH, use {}
$hash{'foo'} = "bar";
# so to define an anonymous hash reference, use {} as well
$hash_ref = { foo => 'bar', xyz => 'abc' };

[download]
So just remember how you access elements in an array/hash, and that will tell you which braces to use for anonymous refs as well. It won't take long for it to become second nature.

blokhead

In reply to Re: The CORRECT thinking behind the {}s and the ()s. by blokhead
in thread The CORRECT thinking behind the {}s and the ()s. by the_Don

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.