Apparently
rob_au knows regexes a little better than you think. (A little tip, while XP doesnt mean a whole lot generally when a saint makes an assertion you should take a little care before you disrespect them without being absolutely sure you are right.)
And since the .+ is greedy, the C will never match.
Wrong. A regex will backtrack the + until the rest of the pattern matches. If the pattern doesnt contain a C then it will fail. The greedyness would only apply if there were more than one C's contained in the string. It would ignore all but the last.
Methinks you owe rob_au an apology and that you should reread perlre.
my @strings=("/^\\\n.....................C",
"/^\\\n............C........C",
"/^\\\n.....................B",
"Foobar");
/(\/\^\\\n.+C)/ && print "---\n\n$1\n---\n\n" foreach @strings;
__END__
---
/^\
.....................C
---
---
/^\
............C........C
---
Yves / DeMerphq
---
Writing a good benchmark isnt as easy as it might look.
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! —
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.