The ideal container program would slurp the regexfile, then apply it to whatever text that is to be searched. In the case of a match, it would somehow be able to retrieve the captured values in the proper order.

Doesn't the following do just that?

my $re = do { local *FILE; open(FILE, '<', $regexp_file_name) or die('...'); local $/; qr/@{[<FILE>]}/ # Compile only once. }; while (<DATA>) { if (@captures = $_ =~ $re) { print(join(', ', @captures), $/); } } __DATA__ abd 123 sdafas 231 gdabd 7364 112 sdafas 785 regexp file (Matches lines with two words of exactly 3 digits.) =========== \b(\d{3})\b.*?\b(\d{3})\b output ====== 123, 231 112, 785

In reply to Re^3: Communication of program(s) with regex codeblocks by ikegami
in thread Communication of program(s) with regex codeblocks by erix

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.