Genius! Madness!
This is such a good idea I'm jealous I didn't have it. No, wait. It's so mind-boggingly hackish I'm glad... Whatever, it's just a very cool hack.
I'll play with it and see how I can make the buffer extension work with it. Current implementation of the module (not on CPAN yet) features a somewhat simpler approach that requires that a match stays exactly the same before and after a buffer extension. Thus, if the user is knowledgeable to use regexes that match delimiters shorter than what they set as the block to read per buffer extension, they're *fairly* safe.
Anyway, I like the ${} approach better even if it's not going to work well. Just for the weirdness of it. :-)

Steffen

In reply to Re: Re: Regexes on Streams by tsee
in thread Regexes on Streams by tsee

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.