You could fix it in both places. I would definitely consider passing a global a bug.
May I also suggest an alternate implementation?
#!/usr/bin/perl
sub trim_start {
for (my $s = @_ ? $_[0] : $_) {
s/\A\s+//m;
return $_;
}
}
sub trim_end {
for (my $s = @_ ? $_[0] : $_) {
s/\s+\z//m;
return $_;
}
}
{
my $test = 'abc , def';
$test =~ /([\s\w]+),([\s\w]+)/;
my @words = map trim_start,
map trim_end,
"$1", "$2";
}
The advantage of that implementation is that its flexible as to how its called.
-
It can be used to trim a single value:
print(trim_start(trim_end($var)), "\n");
-
It can be used to trim a list of values:
my @trimed = map trim_start, map trim_end, @untrimmed;
-
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.
|