> m/([^c]*c)/ will only gobble up until it finds a c, because the c won't
> satisfy ^c; then it matches the c. No backtracking. The non-greedy version (m/(.*?c)/) will
> match zero characters, and then look for a c; then match 1 character, and then look
> for a c; then match match 2 characters, and look for a c; and so on.

This seems to indicate that m/(.*?c)/ and m/([^c]*c)/ will always match the same strings, but the first will be far fatster (in _all_ cases, that I can see at least). So why isn't the first optimized into the second?

I'm probably not seeing somthing here.

Thanks,
James Mastros,
Just Another Perl Initate

In reply to RE: RE: Probably silly regex question / not so silly regex question by theorbtwo
in thread Probably silly regex question / not so silly regex question by theorbtwo

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &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.