You could even just write @$aref in your example.

Post deref can be more useful with more complex expressions like: $myobj->onemethod()->{blue}->anothermethod()->[4]->@* where you can read the thing in the order in which they happen (call onemethod, get the value at "blue", call anothermethod, get the value at 4, then deref), rather than @{ $myobj->onemethod()->{blue}->anothermethod()->[4] } where you read the steps from left to right, and the last one back on the left. I'd use a temp variable in both cases though.

Postderef can also help with slices where $some->{nested}{$complex{struct}}->@{qw<where I want more than one value>} is easier to read than @{$some->{nested}{$complex{struct}}}{qw<where I want more than one value>}. Again a temp variable would be a better idea in both cases IMHO.


In reply to Re^2: I use postfix dereferencing ... by Eily
in thread I use postfix dereferencing ... by hippo

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.