[ViewVC] Diff of: cvs/cvsroot/Async-Interrupt/Interrupt.pm

Comparing cvsroot/Async-Interrupt/Interrupt.pm (file contents):
Revision 1.2 by root, Thu Jul 2 15:13:03 2009 UTC vs.
Revision 1.3 by root, Thu Jul 2 16:12:40 2009 UTC

 SIG_ATOMIC_MAX (guaranteed to allow at least 0..127).
 Since this kind of interruption is fast, but can only interrupt a
 I<running> interpreter, there is optional support for also signalling a
 pipe - that means you can also wait for the pipe to become readable while
+#TODO#
 =over 4
 =cut
 C<$value> must be in the valid range for a C<sig_atomic_t> (0..127 is
 portable).
 =item $async->block
-Sometimes you need a "critical section" of code where
 =item $async->unblock
+Sometimes you need a "critical section" of code that will not be
+interrupted by an Async::Interrupt. This can be implemented by calling C<<
+$async->block >> before the critical section, and C<< $async->unblock >>
+afterwards.
+Note that there must be exactly one call of C<unblock> for ever<y previous
+call to C<block> (i.e. calls can nest).
+Since ensuring this in the presense of exceptions and threads is
+usually more difficult than you imagine, I recommend using C<<
+$async->scoped_block >> instead.
+=item $async->scope_block
+This call C<< $async->block >> and installs a handler that is called when
+the current scope is exited (via an exception, by canceling the Coro
+thread, by calling last/goto etc.).
+This is the recommended (and fastest) way to implement critical sections.
 =cut
 1;

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines