and delighting in the potential for unreadable code coming from using a conditional operator as an lvalue
It takes next to nothing to make the cond op unreadable, but using it as an lvalue itself doesn't make it unreadable.
($axis ? $x : $y) += $distance;
I can't see why 1 ? my $c : my $d would be parsed that way, but 1 ? my $c : $d wouldn't.
It appears to be another case where heuristics enter into play.
my is a valid attribute name, so : my is presumed to be an attribute.
$d is not a valid attribute name, so : $d is taken to be the else expression of the conditional.
Untested, but parens should clear that up.
1 ? (my $c : shared) : ... # shared is an attribute
1 ? (my $c) : shared # shared is func call
perl -MO=Deparse -e 'my $c; 1 ? $c : my $d; $d'
Note that conditionally executing my officially results in undefined behaviour.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.