> goto &{$_[0]->{state} = \&stateReadLit};
Short answer , the author is implementing a state machine.
- &{...} is dereferencing a code-ref
- The subs are the actions per state.
- The goto &NAME syntax guaranties that the call stack isn't needlessly filled up with every state change. (See caller )
- The current state is kept as a code-ref in an attribute of the object ( blessed hash) passed as first argument.
The "weird" code ...
- goto &{$_[0]->{state} = \&stateReadLit};
... could be translated to a more explicit version:
my ($self,...) = @_;
...
my $c_next = $self->{state} = \&stateReadLit; # keep track
goto &{$c_next};
or even
my ($self,...) = @_;
...
$self->{state} = \&stateReadLit;
goto &stateReadLit;
update
Personally I have some doubt about this design decision, it doesn't seem like the code ref in $obj->{state} is ever used for anything more than a Boolean check.
If I was storing a state I'd use a readable name not a ref.
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.