Parents (Total: 2)

The searched file hash is included in 2 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	48D61F185209511478F89B5D922B25FF
PackageArch	x86_64
PackageDescription	For a tutorial-style introduction, please read the Coro::Intro manpage. This manpage mainly contains reference information. This module collection manages continuations in general, most often in the form of cooperative threads (also called coros, or simply "coro" in the documentation). They are similar to kernel threads but don't (in general) run in parallel at the same time even on SMP machines. The specific flavor of thread offered by this module also guarantees you that it will not switch between threads unless necessary, at easily-identified points in your program, so locking and parallel access are rarely an issue, making thread programming much safer and easier than using other thread models. Unlike the so-called "Perl threads" (which are not actually real threads but only the windows process emulation (see section of same name for more details) ported to UNIX, and as such act as processes), Coro provides a full shared address space, which makes communication between threads very easy. And coro threads are fast, too: disabling the Windows process emulation code in your perl and using Coro can easily result in a two to four times speed increase for your programs. A parallel matrix multiplication benchmark (very communication-intensive) runs over 300 times faster on a single core than perls pseudo-threads on a quad core using all four cores. Coro achieves that by supporting multiple running interpreters that share data, which is especially useful to code pseudo-parallel processes and for event-based programming, such as multiple HTTP-GET requests running concurrently. See Coro::AnyEvent to learn more on how to integrate Coro into an event-based environment. In this module, a thread is defined as "callchain + lexical variables + some package variables + C stack), that is, a thread has its own callchain, its own set of lexicals and its own set of perls most important global variables (see Coro::State for more configuration and background info). See also the 'SEE ALSO' section at the end of this document - the Coro module family is quite large.
PackageName	perl-Coro
PackageRelease	1.1
PackageVersion	6.57
SHA-1	015FCAE65C135A4E708EFC05FCA2AFDF932D2183
SHA-256	AC7A7B654BC90C7D6B44943D26141BB65D5607A25D2B07727FBF100A640591BA

Key	Value
MD5	68B3FFE1DEE8E1D7C09548844EB4207B
PackageArch	x86_64
PackageDescription	For a tutorial-style introduction, please read the Coro::Intro manpage. This manpage mainly contains reference information. This module collection manages continuations in general, most often in the form of cooperative threads (also called coros, or simply "coro" in the documentation). They are similar to kernel threads but don't (in general) run in parallel at the same time even on SMP machines. The specific flavor of thread offered by this module also guarantees you that it will not switch between threads unless necessary, at easily-identified points in your program, so locking and parallel access are rarely an issue, making thread programming much safer and easier than using other thread models. Unlike the so-called "Perl threads" (which are not actually real threads but only the windows process emulation (see section of same name for more details) ported to UNIX, and as such act as processes), Coro provides a full shared address space, which makes communication between threads very easy. And coro threads are fast, too: disabling the Windows process emulation code in your perl and using Coro can easily result in a two to four times speed increase for your programs. A parallel matrix multiplication benchmark (very communication-intensive) runs over 300 times faster on a single core than perls pseudo-threads on a quad core using all four cores. Coro achieves that by supporting multiple running interpreters that share data, which is especially useful to code pseudo-parallel processes and for event-based programming, such as multiple HTTP-GET requests running concurrently. See Coro::AnyEvent to learn more on how to integrate Coro into an event-based environment. In this module, a thread is defined as "callchain + lexical variables + some package variables + C stack), that is, a thread has its own callchain, its own set of lexicals and its own set of perls most important global variables (see Coro::State for more configuration and background info). See also the 'SEE ALSO' section at the end of this document - the Coro module family is quite large.
PackageName	perl-Coro
PackageRelease	lp152.1.1
PackageVersion	6.57
SHA-1	6085FDB83CD4523910772B2B3023508CFAB74C66
SHA-256	1D30A52D1501D4AE671D33271E8EADE645A7F0A7BD1C7061BB41BFE000F6C2F1