[poe-commits] poe/lib/POE Kernel.pm,1.278,1.279

[<rc...@us...>]

Update of /cvsroot/poe/poe/lib/POE
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17543/POE

Modified Files:
	Kernel.pm 
Log Message:
Philip Gwyn pointed out that the signal() documentation doesn't match
the full feature set of the method itself.  You can send extra
parameters along with a fake signal, and now the docs reflect that.


Index: Kernel.pm
===================================================================
RCS file: /cvsroot/poe/poe/lib/POE/Kernel.pm,v
retrieving revision 1.278
retrieving revision 1.279
diff -C2 -d -r1.278 -r1.279
*** Kernel.pm	12 Feb 2004 07:30:11 -0000	1.278
--- Kernel.pm	14 Feb 2004 03:45:51 -0000	1.279
***************
*** 2353,2357 ****
    # Post a signal through POE rather than through the underlying OS.
    # This only works within the same process.
!   $kernel->signal( $session, $signal_name );
  
  State (event handler) management methods:
--- 2353,2357 ----
    # Post a signal through POE rather than through the underlying OS.
    # This only works within the same process.
!   $kernel->signal( $session, $signal_name, @optional_args );
  
  State (event handler) management methods:
***************
*** 3188,3192 ****
  interface destruction is just such a non-maskable signal.
  
! Event handlers use C<sig_handled()> to tell POE when a signal has been
  handled.  Some unhandled signals will terminate a program.  Handling
  them is important if that is not desired.
--- 3188,3192 ----
  interface destruction is just such a non-maskable signal.
  
! Event handlers use sig_handled() to tell POE when a signal has been
  handled.  Some unhandled signals will terminate a program.  Handling
  them is important if that is not desired.
***************
*** 3195,3199 ****
  handled, simply by returning some true value.  This is deprecated,
  however, because it has been the source of constant trouble in the
! past.  Please use C<sig_handled()> in its place.
  
  Handled signals will continue to propagate through the parent/child
--- 3195,3199 ----
  handled, simply by returning some true value.  This is deprecated,
  however, because it has been the source of constant trouble in the
! past.  Please use sig_handled() in its place.
  
  Handled signals will continue to propagate through the parent/child
***************
*** 3321,3324 ****
--- 3321,3326 ----
  meaningful within event handlers that are triggered by signals.
  
+ =item signal SESSION, SIGNAL_NAME, OPTIONAL_ARGS
+ 
  =item signal SESSION, SIGNAL_NAME