I can't remember where I read it, but Perl regexes are often faster than c
What do you mean by that? Perls regexp engine is written in C. Is it faster than itself?

Perls regexp engine is a (modified) NFA. It's not hard to come up with matches are screaming fast on a DFA, and takes a long time on an NFA. But an NFA allows one to do things you cannot do with a DFA (writing a regexp matching balanced parenthesis for instance).

like the Perl engine is better developed, it was designed for parsing text,
And what do you mean by that? Do you really think Larry was the only person who said "I got a brilliant idea for a regexp engine. Instead of designing it to do laundry, I will design it to parse text"?

In reply to Re^2: pcre vs perl regex engine by JavaFan
in thread pcre vs perl regex engine by jeteve

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.