Bug #66196 for Class-MethodMaker: Bleadperl v5.13.2-305-gb3f91e9 breaks C:MM 2.16

Sat Feb 26 05:48:38 2011 ANDK [...] cpan.org - Ticket created

Subject:

Bleadperl v5.13.2-305-gb3f91e9 breaks C:MM 2.16

As per subject. Maybe you can learn from RT 60928 Bleadperl b3f91e91 breaks Clone-Closure-0.04_01 because it was broken by the same change. HTH, Best,

Tue Mar 01 08:21:11 2011 schwigon [...] cpan.org - Correspondence added

On Sat Feb 26 05:48:38 2011, ANDK wrote: Show quoted text

> As per subject. > > Maybe you can learn from RT > > 60928 Bleadperl b3f91e91 breaks Clone-Closure-0.04_01 > > because it was broken by the same change. > > HTH, Best,

Thanks. It definitely helped. I did https://github.com/renormalist/class-methodmaker/tree/d5887c407ecbed015c53d6ab03206bcc8f873ba4 to address the issue (with help from the omnipresent rafl). I have some more issues that also break. May I kindly ask whether you could bisect again for me with a newer version of Class::MethodMaker? What would you need for that? Should I upload an intermediate version to CPAN, maybe as a developer release 2.17_01? I could theoretically also bisect myself if you are short on time, but your BBC toolchain seems to be very mature, I can't resist to ask... Thank you very much. Steffen -- Steffen Schwigon <ss5@renormalist.net> Dresden Perl Mongers <http://dresden-pm.org/>

Tue Mar 01 08:21:12 2011 The RT System itself - Status changed from 'new' to 'open'

Tue Mar 01 15:31:37 2011 ANDK [...] cpan.org - Correspondence added

I cannot promise anything but the rule is simply you must release. Whether dev release or stable release does not matter. The normal course of action is that cpantesters smoke and if there is a pattern to discover it will quite often be discovered. If you don't release all of that doesn't happen:)

Wed Mar 02 15:23:47 2011 schwigon [...] cpan.org - Correspondence added

On Tue Mar 01 15:31:37 2011, ANDK wrote: Show quoted text

> I cannot promise anything but the rule is simply you must release.

I just uploaded Class::MethodMaker 2.17. It contains a test that no warnings appear. With it I can see it works on 5.13.1 but fails on 5.13.2. If you would be so kind to bisect this version... Thanks! Kind regards, Steffen -- Steffen Schwigon <ss5@renormalist.net> Dresden Perl Mongers <http://dresden-pm.org/>

Thu Mar 03 01:11:04 2011 ANDK [...] cpan.org - Correspondence added

Git bisect blames v5.13.1-52-gadf8f09 and you can probably learn from ticket 63006: adf8f095c5881bcedf07b8e41072f8125e00b5a6 is the first bad commit commit adf8f095c5881bcedf07b8e41072f8125e00b5a6 Author: Nicholas Clark <nick@ccl4.org> Date: Fri Feb 26 09:18:44 2010 +0000 Set PADSTALE on all lexicals at the end of sub creation. The PADSTALEness of lexicals between the 0th and 1st call to a subroutine is now consistent with the state between the nth and (n + 1)th call. This permits a work around in Perl_padlist_dup() to avoid leaking active pad data into a new thread, whilst still correctly bodging the external references needed by the current ?{} implementation. Fix that, and this can be removed. HTH, Regards,

Tue Apr 19 07:34:02 2011 schwigon [...] cpan.org - Correspondence added

This issue is now solved. Thanks to Andreas König, Florian Ragwitz and Nicholas Clark for support. Steffen -- Steffen Schwigon <ss5@renormalist.net> Dresden Perl Mongers <http://dresden-pm.org/>

Tue Apr 19 07:34:04 2011 schwigon [...] cpan.org - Status changed from 'open' to 'resolved'

Tue Apr 19 07:34:40 2011 schwigon [...] cpan.org - Fixed in 2.18 added