Fix POE::NFA's stop() method. Previously it was using POE::Kernel's

session_free() method, which was recently renamed.

lib/POE/Kernel.pm

@@ -2549,8 +2549,13 @@ sub _dispatch_event {
   # at once.  No, probably not, since GC triggers _stop, which may
   # trigger other GC. -><-
 
+  # Need to test $session for existence because POE::NFA->stop() may
+  # have discarded it already.  -><- This is rapidly becoming a
+  # mess, and some sort of mark/sweep may clean it up.
+
   if ($type & ET_USER) {
-    $self->_data_ses_collect_garbage($session);
+    $self->_data_ses_collect_garbage($session)
+      if $self->_data_ses_exists($session);
     $self->_data_ses_collect_garbage($source_session)
       if ( $session != $source_session and
            $self->_data_ses_exists($source_session)

lib/POE/NFA.pm

@@ -224,7 +224,7 @@ sub _invoke_state {
 
   # Stop request has come through the queue.  Shut us down.
   if ($event eq NFA_EN_STOP) {
-    $POE::Kernel::poe_kernel->session_free( $self );
+    $POE::Kernel::poe_kernel->_data_ses_free( $self );
     return;
   }
 

tests/23_nfa.t

@@ -56,6 +56,18 @@ POE::NFA->spawn
     },
   )->goto_state( initial => 'start' );  # enter the initial state
 
+### This NFA uses the stop() method.  Gabriel Kihlman discovered that
+### POE::NFA lags behind POE::Kernel after 0.24, and stop() wasn't
+### fixed to use the new _data_ses_free() method of POE::Kernel.
+
+POE::NFA->spawn
+  ( inline_states =>
+    { initial =>
+      { start => sub { $_[MACHINE]->stop() }
+      }
+    }
+  )->goto_state(initial => 'start');
+
 ### A plain session to interact with the switch.  It's in its own
 ### package to avoid conflicting constants.  This simulates a causal
 ### observer who pushes the light's button over and over, watching it