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
re.pm clobbers $_ #12202
Comments
From gr@univie.ac.atCreated by gr@univie.ac.atre.pm line 145 clobbers $_. This line is: $_ = $1; when, I believe, it should be: local $_ = $1; The line as it is causes problems if $_ is used in a loop higher up Modification of a read-only value attempted at .../perl-5.16.0/lib/5.16.0/darwin-2level/re.pm line 145. Regardless of where exactly the cause is, I think re.pm shouldn't make Perl Info
|
From @cpansproutOn Tue Jun 19 08:23:36 2012, gr@univie.ac.at wrote:
Yes, you’re right. Ouch! This goes back to 5.13.10: commit b4ab316 re.pm: Add /aa support -- Father Chrysostomos |
The RT System itself - Status changed from 'new' to 'open' |
From @khwilliamsonOn 06/19/2012 09:26 AM, Father Chrysostomos via RT wrote:
The reason this hasn't shown up before is because it clobbers $_ at |
From @doyOn Tue, Jun 19, 2012 at 10:16:57PM -0600, Karl Williamson wrote:
This triggers it: $ perl -E'require re; re->import("/aa") for 1' but it's a bit artificial (although this may be good enough for the -doy |
From @cpansproutOn Tue Jun 19 21:29:01 2012, doy@tozt.net wrote:
I think a better test case could be derived from this: $ ./perl -Ilib -MTest::More=tests,1 -e '$_ = 42; require re; -- Father Chrysostomos |
From @khwilliamsonFixed by commit 48895a0 |
@khwilliamson - Status changed from 'open' to 'resolved' |
From gr@univie.ac.atOn Jun 20, 2012, at 6:28 AM, Jesse Luehrs wrote:
I've figured it out; basically various modules that "use re" are That's the concise explanation; the whole thing happens in tests for Thanks to all involved for the concise test and the fix. Marcel |
Migrated from rt.perl.org#113750 (status was 'resolved')
Searchable as RT113750$
The text was updated successfully, but these errors were encountered: