Name : perl-Thread-Queue
| |
Version : 3.12
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
Release : 1.1
| Date : 2017-03-06 08:07:17
|
Group : Development/Libraries/Perl
| Source RPM : perl-Thread-Queue-3.12-1.1.src.rpm
|
Size : 0.03 MB
| |
Packager : (none)
| |
Summary : Thread-safe queues
|
Description :
This module provides thread-safe FIFO queues that can be accessed safely by any number of threads.
Any data types supported by threads::shared can be passed via queues:
* Ordinary scalars
* Array refs
* Hash refs
* Scalar refs
* Objects based on the above
Ordinary scalars are added to queues as they are.
If not already thread-shared, the other complex data types will be cloned (recursively, if needed, and including any \'bless\'ings and read-only settings) into thread-shared structures before being placed onto a queue.
For example, the following would cause Thread::Queue to create a empty, shared array reference via \'&shared([])\', copy the elements \'foo\', \'bar\' and \'baz\' from \'AATTary\' into it, and then place that shared reference onto the queue:
my AATTary = qw/foo bar baz/; $q->enqueue(\\AATTary);
However, for the following, the items are already shared, so their references are added directly to the queue, and no cloning takes place:
my AATTary :shared = qw/foo bar baz/; $q->enqueue(\\AATTary);
my $obj = &shared({}); $$obj{\'foo\'} = \'bar\'; $$obj{\'qux\'} = 99; bless($obj, \'My::Class\'); $q->enqueue($obj);
See \"LIMITATIONS\" for caveats related to passing objects via queues.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl/openSUSE_13.1/noarch |
Hmm ... It's impossible ;-) This RPM doesn't exist on any FTP server
Provides :
perl(Thread::Queue)
perl-Thread-Queue
Requires :