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";
}
[download]

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");
  [download]

• It can be used to trim a list of values:

  my @trimed = map trim_start, map trim_end, @untrimmed;
  [download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.