Ignoring the issue with newlines and the "s" modifier that I alluded to earlier, the heart of the matter is that "." matches any character while "[^|]" matches any character except the pipe character.

Taken in isolation, /(.*?\|)/ and /([^|]*\|)/ may well produce the same result:

$ perl -Mstrict -Mwarnings -E '
    my $x = q{A|||||Z};
    my $dot_re = qr{(.*?\|)};
    my $cc_re = qr{([^|]*\|)};
    $x =~ $dot_re;
    say $1;
    $x =~ $cc_re;
    say $1;
'
A|
A|
[download]

The reasons they do this, however, are different. "A" is the least number [non-greedy] of zero or more of any characters (".*?") that match before a literal pipe character ("\|"). It just so happens that "A" is also the greatest number [greedy] of zero or more non-pipe characters ("[^|]*") that match before a literal pipe character ("\|"). So, in both cases "A|" is captured.

Now consider the following where the capture groups are no longer in isolation:

$ perl -Mstrict -Mwarnings -E '
    my $x = q{A|||||Z};
    my $dot_re = qr{(.*?\|)Z};
    my $cc_re = qr{([^|]*\|)Z};
    $x =~ $dot_re;
    say $1;
    $x =~ $cc_re;
    say $1;
'
A|||||
|
[download]

Here, "A||||" is the least number [non-greedy] of zero or more of any characters (".*?") that match before a literal pipe character ("\|") that is immediately followed by a literal Z character: "A||||" plus "|" are captured. However, "" (i.e. nothing) is the greatest number [greedy] of zero or more non-pipe characters ("[^|]*") that match before a literal pipe character ("\|") that is immediately followed by a literal Z character: "" plus "|" are captured.

I recommend you take a look at Regexp::Debugger which provides a visualisation of Perl's regular expression engine in action — I think you'll find it most enlightening.

I'd also recommend you look at the Perl documentation (available online at http://perldoc.perl.org/perl.html) before reaching for an internet search engine. Here's a list of Perl regular expression documentation that you'll find linked from that page:

• perlrequick — Perl regular expressions quick start
• perlretut — Perl regular expressions tutorial
• perlfaq6 — Perl frequently asked questions: Regexes
• perlre — Perl regular expressions, the rest of the story
• perlrebackslash — Perl regular expression backslash sequences
• perlrecharclass — Perl regular expression character classes
• perlreref — Perl regular expressions quick reference

That's the order the links appear on that page: look at them in whatever order you want. To be honest, I was a little surprised there was so many; had I realised in advanced, I might not have chosen to start enumerating them all here.

---

---

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.