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.0-246-g13b0f67 breaks LEONT/File-Map-0.57.tar.gz #13080
Comments
From @andkgit bisect 13b0f67 is the first bad commit re-enable Copy-on-Write by default. sample fail report http://www.cpantesters.org/cpan/report/2c57d796-c6d6-11e2-954c-7bff979cd64d perl -V Summary of my perl5 (revision 5 version 19 subversion 1) configuration: | -- |
From @LeontOn Thu, Jul 4, 2013 at 8:28 AM, Andreas J. Koenig via RT
Yeah, or better said blead re-breaks it, for previously discussed Leon |
The RT System itself - Status changed from 'new' to 'open' |
From @cpansproutOn Thu Jul 04 00:05:46 2013, LeonT wrote:
Do you remember which ticket that was in? -- Father Chrysostomos |
From @LeontOn Tue, Aug 20, 2013 at 5:41 PM, Father Chrysostomos via RT <
It was discussed in #115910 Leon |
From @cpansproutOn Tue Aug 20 09:10:47 2013, LeonT wrote:
Thank you. ’Turns out s/// on SvLEN==0 was already broken: $ perl5.18.1 -e 'for(!${\0}) { Internals::SvREADONLY($_,0); s/1/1/; }' -- Father Chrysostomos |
From @cpansproutOn Wed Aug 21 00:01:34 2013, sprout wrote:
Er, please ignore that. It has to do with this logic: /* can do inplace substitution? */ This line prevents the in-place substitution in File::Map’s tests: && (once || !(r_flags & REXEC_COPY_STR)) r_flags & REXEC_COPY_STR is always true now. File::Map fails in earlier I don’t quite understand the logic here. -- Father Chrysostomos |
From @cpansproutOn Wed Aug 21 00:36:09 2013, sprout wrote:
I don’t think that logic is correct or ever was. Match vars can point I removed that line in 1555b32 and File::Map passes its tests again. -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'resolved' |
From @cpansproutOn Wed Aug 21 22:45:13 2013, sprout wrote:
That fix turned out to be wrong, so I redid it in 9cefd26. -- Father Chrysostomos |
Migrated from rt.perl.org#118747 (status was 'resolved')
Searchable as RT118747$
The text was updated successfully, but these errors were encountered: