On 06/12/2013 11:28 AM, Salvador FandiƱo via RT wrote: > ----- Original Message ----- >> From: Ricardo Signes <perl.p5p@rjbs.manxome.org> >> To: Salvador Fandino <sfandino@yahoo.com> >> Cc: perl5-porters@perl.org >> Sent: Friday, June 7, 2013 6:19 PM >> Subject: Re: Storable refactoring, was Re: [perl #118139] Storable in DESTROY > blocks >> >> * Salvador Fandino <sfandino@yahoo.com> [2013-05-29T13:22:17] >>> I have been working for some time in refactoring Storable. See >>> >>> https://github.com/salva/perl5/tree/improve_storable >> >> Wow, no kidding! It looks like you've gotten some feedback on this, please >> let >> me know if you need anything specific to help things move foward. > > > I have applied the patch from Nicholas Clark and also solved the problems found by Peter Rabbitson. The test suite passes on any perl from 5.6.0 upward (*). I have run it on hundreds of different perls (do you know about the new perlbrew feature "install-multiple"?) > > At this point I think the module is ready to be released to CPAN as a development version so that it gets stressed by the CPAN Testers or anybody that want to give it a try. > > So, could I have comaintainership of the module assigned so that it doesn't appear as a unauthorized release? > > Also, is the CPAN package stored in some version control system somewhere? I tracked the cpan history and latest blead and your patches in git@github.com:rurban/Storable.git Can you fix the ChangeLog entry? But I'm still working on some pointer-sign problems in your changes. And you cannot just remove the hints to fix gcc -O3 optimizer problems. -- Reini Working towards a true Modern Perl. Slim, functional, unbloated, compile-time optimizableThread Previous | Thread Next