New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bleadperl v5.19.11-90-gd3f8a93 breaks ZEFRAM/Sub-Mutate-0.005.tar.gz #13841
Comments
From @andkgit bisect commit d3f8a93 Revert "[perl #79908] Stop sub inlining from breaking closures" diagnostics http://www.cpantesters.org/cpan/report/7301af04-dba8-11e3-a971-af1773305bfd rt.cpan ticket https://rt.cpan.org/Ticket/Display.html?id=95649 perl -V Summary of my perl5 (revision 5 version 19 subversion 12) configuration: Characteristics of this binary (from libperl): -- |
From @jkeenanOn Wed May 14 19:35:16 2014, andreas.koenig.7os6VVqR@franz.ak.mind.de wrote:
[snip] I tried this on blead (commit 097675b) with khw's test program. I did not even get as far as Andreas got with 5.19.11. ##### $ ./Build ##### |
The RT System itself - Status changed from 'new' to 'open' |
From @khwilliamsonOn 6/9/2014 7:11 PM, James E Keenan via RT wrote:
just remove the PL_sv_objcount. It is no longer used by the core. |
From @nwc10On Mon, Jun 09, 2014 at 07:52:43PM -0600, Karl Williamson wrote:
This isn't quite correct. It was in use prior to this commit: commit ddf23d4 Prepare PL_sv_objcount removal This used to keep track of all objects. At least by now, that is The interpreter global will remain for one deprecation cycle. So the pedantically correct approach would be to wrap the code that accesses #if PERL_VERSION < 18 (Not tested) *However*, I think that it won't make any behaviour difference just removing Nicholas Clark |
From @jkeenanOn Mon Jun 09 23:50:18 2014, nicholas wrote:
I'm confused as to what action, if any, P5P needs to take with respect to the issues raised in this ticket. Can anyone clarify? How do we move the ticket toward resolution? Thank you very much. -- |
From @iabynOn Sun, Sep 14, 2014 at 05:33:34AM -0700, James E Keenan via RT wrote:
The conclusion seems to be that its not a perl bug, and that the module #if PERL_VERSION < 18 -- |
From @jkeenanMarking ticket resolved per comment from Dave M. |
@jkeenan - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#121876 (status was 'resolved')
Searchable as RT121876$
The text was updated successfully, but these errors were encountered: