Bug #111466 for Scalar-List-Utils: polyfill from Sub::Current

Wed Jan 27 15:18:07 2016 JBERGER [...] cpan.org - Ticket created

CC:	stevan.little [...] gmail.com

Sub::Current provides an xsub (ROUTINE) which if distributed as part of (core) Sub::Util would make an excellent polyfill for __SUB__ in pre-5.16 perls. I would suggest (if possible) to actually treat it as a polyfill, exporting the xsub as __SUB__ in those environments or enabling current_sub feature in 5.16+

Wed Jan 27 15:57:10 2016 ether [...] cpan.org - Subject changed from (no value) to 'polyfill from Sub::Current'

Mon Feb 01 14:00:53 2016 stevan.little [...] gmail.com - Correspondence added

Completely agree with Joel on this, it would be a nice feature and for very little effort since the code is already written. +1 On Wed Jan 27 15:18:07 2016, JBERGER wrote: Show quoted text

> Sub::Current provides an xsub (ROUTINE) which if distributed as part > of (core) Sub::Util would make an excellent polyfill for __SUB__ in > pre-5.16 perls. I would suggest (if possible) to actually treat it as > a polyfill, exporting the xsub as __SUB__ in those environments or > enabling current_sub feature in 5.16+

Mon Feb 01 14:00:54 2016 The RT System itself - Status changed from 'new' to 'open'

Mon Feb 01 14:08:34 2016 leonerd-cpan [...] leonerd.org.uk - Correspondence added

On Wed Jan 27 15:18:07 2016, JBERGER wrote: Show quoted text

> Sub::Current provides an xsub (ROUTINE) which if distributed as part > of (core) Sub::Util would make an excellent polyfill for __SUB__ in > pre-5.16 perls. I would suggest (if possible) to actually treat it as > a polyfill, exporting the xsub as __SUB__ in those environments or > enabling current_sub feature in 5.16+

Yup; that sounds good. -- Paul Evans