Parents (Total: 9)

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

Key	Value
MD5	8F8D341843BA61D0634DB08B3DA2B9F0
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.3
PackageVersion	6.57
SHA-1	879FEBAEE6EEE97919B9EE76A34AF30117DF4F2B
SHA-256	C655FE4642ACECF016C4061B271CBF28C502D6598FBA2C5BB21895BC7B4A1810

Key	Value
MD5	3E76E4EE8E8AB25E6C3F2B754BD42E2B
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	lp150.1.1
PackageVersion	6.57
SHA-1	942E476B7D384EA33B933EFB6FF7B42EE8D094A8
SHA-256	F8C0AF0808A510C1C8ABE322CECF432967C9FB21570EA1A9C8D0E269673C2102

Key	Value
MD5	4BC5181151B8DF1C9F33BA858899FC77
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	C1F339296321C7EDD7710B18A1DE7F4F43219F1D
SHA-256	83790BCDF8CA43B0B6A8573270AE5DE363833CD7C4E7C937E43656FC8073D839

Key	Value
MD5	DE4F4BD3DA3CCDD16B10D5CD15CC1D72
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	lp151.1.1
PackageVersion	6.57
SHA-1	DC0E2026864B5C1EE1F73B894B8BFD9BE03E0AAC
SHA-256	80BC56B43F6DFBFA2D7528632D38160BE5B87DA428B70D0CDC1F10EE3A32618F

Key	Value
MD5	6C3E6AC661D8DA9F0960DFE1DD9B9C2A
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	lp153.1.9
PackageVersion	6.57
SHA-1	657916B50DD2F5D91F16D6F5FC9E093041414EC5
SHA-256	53B77E9D1EC5FE7E2A1CBC74C7C9BBA4857EE78D5BF420C3956A9E4705EE30A0

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

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	498D935D133E2D9F19ACBC2B07EF8EE4
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	D959863FBAD5CAB35FAADF5F1C5616C6F9551CE3
SHA-256	89A3198104E75BEAB4CA985F641FE94546F6663AA96488E7DABB43B0B80F52AA

Key	Value
MD5	18591C7C84BC36F06A90481A0FBCDD02
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.3
PackageVersion	6.57
SHA-1	4D2606400B9286CC2919BF89A06FE7780D82F188
SHA-256	34E7940C44F78913565CFFA5D96467B7D43CCDDA6513BAF41972DD2F5CA2BD34