Hi Foodeywo

I would discourage using /o modifier, because of this note in perlre for v5.22:

  o  - pretend to optimize your code, but actually introduce bugs

using qr// is much better practice, as you can control when the compilation happens. If you want to know exactly how perl handles your regexps you can use:

perl -Mre=debug -d -ne 'print if (/MYLARGEREGEX_HERE/../END_OF_BLOCK/)' inputfile > outputfile

-Mre=debug gives you nice output about regex compilation and matching
and
-d puts you into debugger.

Go through your program step by step with "s" debugger option.

Happy hacking,
natan

---- PS: my first post on PerlMonks. Hello everybody!

In reply to Re: Performance of assambled regex by natan
in thread Performance of assambled regex by Foodeywo

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.