Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Re: Upgrade to 5.18 causes uninitialized ${^MATCH}

by AnomalousMonk (Canon)
on May 28, 2013 at 02:24 UTC ( #1035506=note: print w/replies, xml ) Need Help??

in reply to Upgrade to 5.18 causes uninitialized ${^MATCH}

It's possible for either or both of pos or  ${^MATCH} to be undefined after a match, which is easily demonstrated (Perl version 5.14):

>perl -wMstrict -le "my @strs = (qw(123x foo ***), ''); ;; for my $s (@strs) { $s =~ m{ \d+ }xmsgp; printf qq{for '%s': pos == %s, \${^MATCH} eq '%s' \n}, $s, pos($s) // 'undefined', ${^MATCH} // 'undefined', ; } " for '123x': pos == 3, ${^MATCH} eq '123' for 'foo': pos == undefined, ${^MATCH} eq 'undefined' for '***': pos == undefined, ${^MATCH} eq 'undefined' for '': pos == undefined, ${^MATCH} eq 'undefined'

Rather than Perl, I think the most likely explanation is that the data you are processing has changed.

Update: ... and the length of an undef is undefined.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1035506]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others cooling their heels in the Monastery: (6)
As of 2017-03-24 14:28 GMT
Find Nodes?
    Voting Booth?
    Should Pluto Get Its Planethood Back?

    Results (304 votes). Check out past polls.