I've come across another strange wrinkle in this regex driven dispatch that I've been adding to.

I have two lines of representative text:

111 MatchMe [This is why]
222 I need to be dispatched to the same callback: For This Reason

[download]

What I want (and don't think I should reasonably expect) is an expression that behaves precisely as the following two expressions: 

^(\d+) MatchMe \[(.*)\]$
^(\d+) I need to be dispatched.*\:\s(.*)$

[download]

So those two will match the appropriate lines just duckily. Plus (and more importantly) the values of the $1 and $2 registers are the number and what we'll call the "reason description" (because...uhm... that's what it is.)

I attempted to do this (well, I did it.):

^(\d+) (MatchMe \[(.*)\]$)|(I need to be dispatched.*\:\s(.*)$)

And that will match both lines just fine. But the contents of the registers is, as you might expect, messy (read: values in different places depending on which line is being matched.)

Am I just trying to stretch the semantics of a single regex match too far in my attempt to not disturb the underlying driver code?

What I would LOVE to do is get in there and muck with the driver so I could have N expressions match any particular callback. But frankly I don't think that option is available to me (it's very late in the game and that's very well established core driver code.)

Any fun creative insights?


Thanks again,

- V
uccu

In reply to multiple-line match mucking with regex registers by Voronich

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.