There are several things you can do for efficiency: not much for elegance.

  1. As you read each line from the file, study it.
  2. Apply qr// to each of @patterns.
  3. Do not combine @patterns into a larger pattern. Iterate instead
  4. Quit iterating at the first match.
  5. Keep score. Sort @patterns so that the commonest matches come first.

Not all these will help or may apply. For instance, a parser may have fixed priorities for matches, preventing use of #5. As for the others, Benchmark. Strategy #4 is observed by the big alternation, so should be used in any iterative scheme, too..

Update: Bah, underspecified. It sounds like you want an rdbms and DBI to store your data. RMGir's hash idea is good too.

After Compline,
Zaxo

In reply to Re: Bulk Regex? by Zaxo
in thread Bulk Regex? by meetraz

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.