Beta Shell v2.0

File Manager

Name	Size	Perms	Modified	Actions
[ .. / .. ]
AIO.pm	4.82 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
AnyEvent.pm	13.28 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
BDB.pm	1.48 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Channel.pm	3.96 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
CoroAPI.h	5.1 KB	-rw-r--r--	2020-03-11 09:47:09	Edit Del
Debug.pm	16.07 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
EV.pm	2.56 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Event.pm	5.3 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Handle.pm	13.5 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Intro.pod	26.15 KB	-rw-r--r--	2017-07-14 03:02:45	Edit Del
LWP.pm	3.92 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
MakeMaker.pm	3.66 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
RWLock.pm	2.26 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Select.pm	3.69 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Semaphore.pm	4.3 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
SemaphoreSet.pm	4.1 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Signal.pm	2.24 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Socket.pm	5.34 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Specific.pm	1.79 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
State.pm	18.98 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Storable.pm	3.68 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Timer.pm	1.62 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
Util.pm	5.44 KB	-rw-r--r--	2020-07-29 13:08:58	Edit Del
jit-amd64-unix.pl	2.69 KB	-rw-r--r--	2021-03-04 15:26:29	Edit Del
jit-x86-unix.pl	2.89 KB	-rw-r--r--	2021-03-04 15:26:29	Edit Del

Editing: Specific.pm (1.79 KB)

=head1 NAME

Coro::Specific - manage coroutine-specific variables.

=head1 SYNOPSIS

 use Coro::Specific;

 my $ref = new Coro::Specific;

 $$ref = 5;
 print $$ref;

=head1 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 C<%$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 L<Coro> module - when Coro is loaded, the keys stored in
C<%$Coro::current> are automatically attached to the coro thread executing
the main program.

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

=over 4

=cut

package Coro::Specific;

use common::sense;

our $VERSION = 6.57;

=item new

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

=cut

my $idx;

sub new {
   my $var;
   tie $var, Coro::Specific::;
   \$var;
}

sub TIESCALAR {
   my $idx = $idx++;
   bless \$idx, $_[0];
}

sub FETCH {
   $Coro::current->{_specific}[${$_[0]}];
}

sub STORE {
   $Coro::current->{_specific}[${$_[0]}] = $_[1];
}

#sub DESTROY {
#   push @idx, $$_[0];
#}

1;

=back

=head1 BUGS

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

=head1 AUTHOR/SUPPORT/CONTACT

   Marc A. Lehmann <schmorp@schmorp.de>
   http://software.schmorp.de/pkg/Coro.html

=cut