develooper Front page | perl.perl5.porters | Postings from September 2011

Re: The future of POSIX in core

Thread Previous | Thread Next
David Golden
September 2, 2011 07:27
Re: The future of POSIX in core
Message ID:
On Fri, Sep 2, 2011 at 10:04 AM, Mark Overmeer <> wrote:
> Counting back from Feb/2012 there must be a moment not too far away
> when the user-visible changes get frozen. So, about when?
> The whole purpose of this thread was to check with "Core" what would
> be the best way to get the changes into 5.16. Where goes what. Still
> not completely sure where the consensus will get us.

For Perl 5.14, the "contentious change" freeze was late December 2010.
 The "user-visible change" freeze was late Feb 2011.  The "hard"
freeze to start the RC cycle was late March 2011.

I haven't seen anybody object to a documentation patch for
I would suggest submitting that as a distinct patch.  I will commit to
personally reviewing it and providing feedback (or else I will just
commit it if I think it's close enough).

I have no objection to splitting out POSIX::SigAction and POSIX::SigRT
into separate .pm files that are used by  (I.e. loading
POSIX should load those also.) I would accept a patch for that.

I don't hear consensus for changing the POSIX @EXPORT API.  I think
that is not going to get sufficient support.

There is the outstanding proposal for applying the correct prototypes
to POSIX clones of Perl functions.  Given the disagreement, I think we
need Jesse to make a call.   I suggest creating a new thread on that
topic specifically and ask him to render judgment.

Are there any other issues outstanding?

-- David

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