Hi all
Is this a bug, or just a bad regex?
sub match {
no warnings;
my $value = shift @_;
$value =~ s{^(?:aa(bb))?.*}{$1}i;
return $value;
}
sub match_warn {
use warnings;
my $value = shift @_;
$value =~ s{^(?:aa(bb))?.*}{$1}i;
return $value;
}
print match('aabbcc')."\n"; # 'bb'
print match('abbcc')."\n"; # ''
print match_warn('aabbcc')."\n"; # 'bb'
print match_warn('abbcc')."\n"; # Use of uninitialized value $1
+in substitution iterator
The way I would have read that is that the capture would contain the empty string, rather than undef and so wouldn't have thrown an unintialized value warning. Is my assumption correct, which would mean that this is a bug (in 5.8.8 and 5.10), or is there a better way to write this regex.
(Note: this regex is a simplified example of a substitution which is intended to retain a part of a string (if the surrounding text matches), and if not, to set the string to the empty string).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|