coro::specific(3pm) [debian man page]

Specific(3pm)						User Contributed Perl Documentation					     Specific(3pm)

NAME

       Coro::Specific - manage coroutine-specific variables.

SYNOPSIS

	use Coro::Specific;

	my $ref = new Coro::Specific;

	$$ref = 5;
	print $$ref;

DESCRIPTION

       This module can be used to create variables (or better: references to them) that are specific to the currently executing coroutine. This
       module does not automatically load the Coro module (so the overhead will be small when no coroutines are used).

       A much faster method is to store extra keys into %$Coro::current - all you have to do is to make sure that the key is unique (e.g. by
       prefixing it with your module name). You can even store data there before loading the Coro module - when Coro is loaded, the keys stored in
       %$Coro::current are automatically attached to the coro thread executing the main program.

       You don't have to load "Coro::Specific" manually, it will be loaded automatically when you "use Coro" and call the "new" constructor.

       new Create a new coroutine-specific scalar and return a reference to it. The scalar is guarenteed to be "undef". Once such a scalar has
	   been allocated you cannot deallocate it (yet), so allocate only when you must.

BUGS

       The actual coroutine specific values do not automatically get destroyed when the Coro::Specific object gets destroyed.

AUTHOR

	Marc Lehmann <schmorp@schmorp.de>
	http://home.schmorp.de/

perl v5.14.2							    2012-04-13							     Specific(3pm)

Signal(3pm)						User Contributed Perl Documentation					       Signal(3pm)

NAME

       Coro::Signal - thread signals (binary semaphores)

SYNOPSIS

	use Coro;

	$sig = new Coro::Signal;

	$sig->wait; # wait for signal

	# ... some other "thread"

	$sig->send;

DESCRIPTION

       This module implements signals/binary semaphores/condition variables (basically all the same thing). You can wait for a signal to occur or
       send it, in which case it will wake up one waiter, or it can be broadcast, waking up all waiters.

       It is recommended not to mix "send" and "broadcast" calls on the same "Coro::Signal" - it should work as documented, but it can easily
       confuse you :->

       You don't have to load "Coro::Signal" manually, it will be loaded automatically when you "use Coro" and call the "new" constructor.

       $sig = new Coro::Signal;
	   Create a new signal.

       $sig->wait
	   Wait for the signal to occur (via either "send" or "broadcast"). Returns immediately if the signal has been sent before.

       $sem->wait ($callback)
	   If you pass a callback argument to "wait", it will not wait, but immediately return. The callback will be called under the same
	   conditions as "wait" without arguments would continue the thrad.

	   The callback might wake up any number of threads, but is NOT allowed to block (switch to other threads).

       $sig->send
	   Send the signal, waking up one waiting process or remember the signal if no process is waiting.

       $sig->broadcast
	   Send the signal, waking up all waiting process. If no process is waiting the signal is lost.

       $sig->awaited
	   Return true when the signal is being awaited by some process.

AUTHOR

	Marc Lehmann <schmorp@schmorp.de>
	http://home.schmorp.de/

perl v5.14.2							    2012-04-13							       Signal(3pm)