That's only a bonus if you can switch packages without a semicolon.
Oh yeah. Well, no bonus, but it still makes it more readable.
I'm surprised this works.
Me too, but it makes sense. It allows for
our $state = $next_states{$state};
Unfortunally, it's not a general technique.
Oops! Just replace the and op with a list op or replace the sassign op with an aassign op.
(local our $n = shift), ...
or
(local (our $n) = shift) && ...
The former is simpler. The latter has the advantage that it doesn't affect the return value in list context.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.