I'm responding again to this idea because your suggestion gained traction with me as I puzzled out a solution. I managed to eliminate the counters, as you suggested, and the code executes more efficiently now. Here's what that portion is now reduced to:
next if ( ($regex1)
&& ( (($accpyn1) && ($line1 !~ m/$regex1/o))
|| (!($accpyn1) && ($line1 =~ m/$regex1/o)) )
);
next if ( ($regex2)
&& ( (($accpyn2) && ($line2 !~ m/$regex2/o))
|| (!($accpyn2) && ($line2 =~ m/$regex2/o)) )
);
next if ( ($regex3)
&& ( (($accpyn3) && ($line3 !~ m/$regex3/o))
|| (!($accpyn3) && ($line3 =~ m/$regex3/o)) )
);
next if ( ($regex4)
&& ( (($accpyn4) && ($line4 !~ m/$regex4/o))
|| (!($accpyn4) && ($line4 =~ m/$regex4/o)) )
);
And with that logic, the counters became unnecessary. So thank you for the suggestion--it has been put to practical use.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.