The for is apparently just being used as a topicalizer here. So if you rewrite the first code example in "normal" Perl, it's

if ( $sFunction =~ /test1/ ) { # ... } if ( $sFunction =~ /test2/ ) { # ... }

So then it becomes more clear that one possibility of several for rewriting the logic is the following, where one could even consider to put $sFunction =~ /test2/ into a variable to avoid invoking the regex engine twice:

if ( $sFunction =~ /test1/ || $sFunction =~ /test2/ ) { # ... if ( $sFunction =~ /test2/ ) { # ... } }

Or, assuming your regexes have something in common like these example regexes, you can even write something like:

if ( my ($num) = $sFunction =~ /test([12])/ ) { # ... if ( $num eq "2" ) { # ... } }

In reply to Re: recursive call of current script by haukex
in thread recursive call of current script by feumw

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.