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
Improper modification of hash during each() traversal in t/basic.t in ExtUtils-MakeMaker in 5.17.9 with hash traversal order randomization #12796
Comments
From @demerphqIMO this should be viewed as a 5.18 blocker. It is buggy to start, but in 5.18 with hash traversal order Cheers, ---------- Forwarded message ---------- Greetings, This message has been automatically generated in response to the There is no need to reply to this message right now. Your ticket has been https://rt.cpan.org/Ticket/Display.html?id=83441 Please include the string: [rt.cpan.org #83441] in the subject line of all future correspondence about this issue. To do so, Thank you, t/basic.t contains a subroutine called _normalize() which uses faulty This has never been legal, but due to implementation issues probably Changes coming in Perl 5.18 mean that this will fail regularly. Attached patch fixes the problem. This is a Perl 5.18 blocker ticket, so I am marking it as important. -- |
From @jkeenanOn Tue Feb 19 04:03:51 2013, demerphq wrote:
Schwern accepted the patch in this pull: Perl-Toolchain-Gang/ExtUtils-MakeMaker@6e09ca2 I believe that means what remains to be done is: (a) Updated version of ExtUtils::MakeMaker released to CPAN; (b) We pull that version into Perl 5 blead. Correct? |
The RT System itself - Status changed from 'new' to 'open' |
From @demerphqOn 24 February 2013 00:53, James E Keenan via RT
Yes, except that we are also waiting on a second PR to be applied Yves -- |
From @rjbsFixed in ExtUtils-MakeMaker-6.65_01, now in blead. -- |
From [Unknown Contact. See original ticket]Fixed in ExtUtils-MakeMaker-6.65_01, now in blead. -- |
@rjbs - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#116857 (status was 'resolved')
Searchable as RT116857$
The text was updated successfully, but these errors were encountered: