develooper Front page | perl.perl5.porters | Postings from January 2012

Re: What to do with POSIX::SigRt?

Thread Previous | Thread Next
Leon Timmermans
January 9, 2012 12:45
Re: What to do with POSIX::SigRt?
Message ID:
On Mon, Jan 9, 2012 at 3:54 PM, Nicholas Clark <> wrote:
> Depends if we want to kill it dead, or simply push it out onto CPAN much
> like Switch or Devel::DProf.
> Pushing it onto CPAN seems "nicer", but a bit harder.
> Currently has
>    tie %POSIX::SIGRT, 'POSIX::SigRt';
> I think we'd need to break out the code implementing this, ie that in
> package POSIX::SigRT, out into its own .pm file.
> For a transition period, to keep things working, we'd then need to have
> tie %POSIX::SIGRT to a bunch of proxy code that loads POSIX::SigRT
> but warns you that you should have done this yourself.
> Then, after a release or two we drop the proxying code.
> Likely, in parallel, one would have POSIX::SigRT be in dist/ dual-life
> on CPAN, and going through the "evicting module from core" process.

Sounds like a sane plan

>    B<NOTE:> whether POSIX realtime signals really work in your system, or
>    whether Perl has been compiled so that it works with them, is outside
>    of this discussion.
> which likely *also* means that we can't test it.

There are some tests for it already in POSIX's test suite. If SIGRTMIN
and SIGRTMAX are present and sensible you can assume the OS has real
time signals.


Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About