Just a quick note on using lexicals in those regex closures. The trouble was that the lexicals were seen sometimes. I could not find out when they were seen I<exactly>. If those regex code constructs worked alright as closures, they would have seen the lexicals I<all the time> because the closures were declared and used I<in the same scope> that the lexical was declared. What happened was, usually the first two times the regular expression engine executed the closure, the lexical would be incremented, and after that, the code would still be executed (print() worked), but the lexicals weren't touched. (I tried it with a tied lexical that warns when touched, too.)

Steffen

In reply to Re: Re^3: Regexes on Streams - Revisited! by tsee
in thread Regexes on Streams - Revisited! 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.