I tried to do that by including the several lines preceding the regex (the while loop) in the test program, which compiled and ran. So I must not have grabbed code back far enough to include the error.

I cut and pasted the entire subroutine containing the while loop. Lo and behold I found the problem: this is a CGI script (which is why taint checking is on) and I forgot the $ on my CGI object, five lines above my while loop. So instead of "$q->p()" I had "q->p()". Aargh.

The lesson to be learned here is when you are done looking for missing semicolons and string delimiters, look next for missing dollar signs on variables (especially objects).

Thanks much for breaking me out of a "tight mental loop" around that damned regex. ;-)

In reply to Re: Re: Regex syntax frustration by bigmacbear
in thread Solved: Regex syntax frustration by bigmacbear

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.