It's short, elegant, and gets the job done.
Sounds like typical Perl to me.
Will it confuse people
No doubt it will confuse people. It's almost impossible to write some code that doesn't confuse people. And there will always be people (and unfortunally, relatively more of them can be found on perlmonks) who try to enforce some arbitrary rules on how people should code because it otherwise confuses them (although they try to claim it confuses everyone else as well). Example where this happens:
is it just bad practice in general to rely on the order of evaluations?
Not at all. It's only bad practice to rely on the order of evaluation if the order isn't defined. But the order is defined in your case. From perlop: 
Operator associativity defines what happens if a sequence of the same
operators is used one after another: whether the evaluator will evalu-
ate the left operations first or the right.  For example, in "8 - 4 -
2", subtraction is left associative so Perl evaluates the expression
left to right. "8 - 4" is evaluated first making the expression "4 - 2
== 2" and not "8 - 2 == 6".

[download]
And then, skipping a paragraph, it defines -> to be left associative.

In reply to Re: One line accessor method style. by Anonymous Monk
in thread One line accessor method style. by Anonymous Monk

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.