On Fri, Apr 10, 2009 at 11:11:10AM +0200, Simon Bertrang wrote:
> On Thu, Apr 09, 2009 at 07:45:08PM -0700, James Wright wrote:
> > Attached ports of p5-forks and its dependencies (Sys::SigAction and
> > Acme::Damn):
> >
> > $ cat devel/p5-forks/pkg/DESCR
> > The "forks" pragma allows a developer to use threads without having to
> > have a threaded perl, or to even run 5.8.0 or higher.
> >
> > Refer to the threads module for ithreads API documentation.
> > $ cat devel/p5-Sys-SigAction/pkg/DESCR
> > Sys::SigAction provides an easy mechanism for the user to recover the
> > pre-5.8.0 behavior for signal handling. This module wraps up the
> > POSIX:: routines and objects necessary to call sigaction() in a way
> > that is as efficient from a coding perspective as just setting a
> > localized $SIG{SIGNAL} with a code reference. Further, the user has
> > control over the sa_flags passed to sigaction(). By default, if no
> > additional args are passed to sigaction(), then the signal handler
> > will be called when a signal (such as SIGALRM) is delivered.
> > $ cat devel/p5-Acme-Damn/pkg/DESCR
> > Acme::Damn provides a single routine, damn(), which takes a blessed
> > reference (a Perl object), and unblesses it, to return the original
> > reference. I can't think of any reason why you might want to do this,
> > but just because it's of no use doesn't mean that you shouldn't be
> > able to do it.
> >
> > Forks is currently API compatible with CPAN threads version 1.53 (current
> > perl threads module is 1.67). All modules pass regress (p5-forks regress
> > takes a while to complete). Tested on i386.
> >
>
> We have devel/p5-forks already, can you bake a diff instead? :-)
>
Dooooh, sorry... jasper@ pointed out i'm wrong - it's in my main tree
instead of mystuff. Expect feedback soon :-)
Regards,
Simon
