I do a lot of conditional testing, such as:
if ($x == 1) { $abc = 1 } elsif ($x == 2) { $def = 1 } elsif ($x == 3) { $xyz = 1 } else { $nothing = 1 }
but in reading Prog. Perl (p. 125) I see this could send me to the confessional. So, I tried:
SWITCH: { if ($x == 1) { $abc = 1; last SWITCH; }; if ($x == 2) { $def = 1; last SWITCH; }; if ($x == 3) { $xyz = 1; last SWITCH; }; $nothing = 1; }
or
SWITCH: for ($x) { if (1) { $abc = 1; last SWITCH; }; if (2) { $def = 1; last SWITCH; }; if (3) { $xyz = 1; last SWITCH; }; $nothing = 1; }
Sure it looks nicer, but in speed tests, depending on how $x is set, this later structure always slower, and in some cases significantly.

My question, what am I missing here? The if/else structure actually looks cleaner to me and if it's faster...

Thanks, monks of greater XP.

bradcathey

In reply to Use of SWITCH vs IF ELSE in speed and readability by bradcathey

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.