Permalink
Browse files

Moved documentation change to a less illogical spot.

  • Loading branch information...
hubie committed Apr 24, 2012
1 parent ffbd225 commit 71b16471861a87cbf0fe519b18c421d936392884
Showing with 5 additions and 5 deletions.
  1. +5 −5 lib/POE/NFA.pm
View
@@ -969,6 +969,11 @@ The C<runstate> parameter allows C<RUNSTATE> to be initialized differently
at instantiation time. C<RUNSTATE>, like heaps, are usually anonymous hashrefs, at instantiation time. C<RUNSTATE>, like heaps, are usually anonymous hashrefs,
but C<runstate> may set them to be array references or even objects. but C<runstate> may set them to be array references or even objects.
State transitions are not necessarily executed immediately by default. Rather,
they are placed in POEs event queue behind any currently pending events.
Enabling the C<immediate> option causes state transitions to occur immediately,
regardless of any queued events.
=head2 goto_state NEW_STATE[, ENTRY_EVENT[, EVENT_ARGS]] =head2 goto_state NEW_STATE[, ENTRY_EVENT[, EVENT_ARGS]]
goto_state() puts the machine into a new state. If an ENTRY_EVENT is goto_state() puts the machine into a new state. If an ENTRY_EVENT is
@@ -985,11 +990,6 @@ event's handler via C<ARG0..$#_>.
# Switch to the next state; call an entry point with some values. # Switch to the next state; call an entry point with some values.
$_[MACHINE]->goto_state( 'next_state', 'entry_event', @parameters ); $_[MACHINE]->goto_state( 'next_state', 'entry_event', @parameters );
State transitions are not necessarily executed immediately by default. Rather,
they are placed in POEs event queue behind any currently pending events.
Enabling the C<immediate> option causes state transitions to occur immediately,
regardless of any queued events.
=head2 stop =head2 stop
stop() forces a machine to stop. The machine will also stop stop() forces a machine to stop. The machine will also stop

0 comments on commit 71b1647

Please sign in to comment.