pkgsrc/devel/p5-Mojo-IOLoop-ForkCall/PLIST

@comment $NetBSD: PLIST,v 1.1 2014/08/30 10:53:51 wiedi Exp $
${PERL5_SUB_INSTALLVENDORLIB}/Mojo/IOLoop/ForkCall.pm
${PERL5_SUB_INSTALLVENDORARCH}/auto/Mojo/IOLoop/ForkCall/.packlist
${PERL5_SUB_INSTALLVENDORMAN3DIR}/Mojo::IOLoop::ForkCall.3
Import p5-Mojo-IOLoop-ForkCall-0.14 as devel/p5-Mojo-IOLoop-ForkCall Asynchronous programming can be benefitial for performance, however not all functions are written for nonblocking interaction and external processes almost never are. By forking the blocking call into a new process, the main thread may continue to run non-blocking, while the blocking call evaluates. Mojo::IOLoop::ForkCall manages the forking and will emit an event (or execute a callback) when the forked process completes. Return values are serialized and sent from the child to the parent via an appropriate pipe for your platform. 2014-08-30 12:53:51 +02:00			`@comment $NetBSD: PLIST,v 1.1 2014/08/30 10:53:51 wiedi Exp $`
			`${PERL5_SUB_INSTALLVENDORLIB}/Mojo/IOLoop/ForkCall.pm`
			`${PERL5_SUB_INSTALLVENDORARCH}/auto/Mojo/IOLoop/ForkCall/.packlist`
			`${PERL5_SUB_INSTALLVENDORMAN3DIR}/Mojo::IOLoop::ForkCall.3`