And the B::Deparse module can be handy when trying to figure out why when something's not behaving the way you expect. I show running over code given in a shell here-doc, but you can do the same thing to code in a file via perl -MO=Deparse,-p my_file.plx. 

$ perl -MO=Deparse,-p <<'EOT'
if ($answer eq "add" || "a") {
&addlinks;
} elsif ($answer eq "remove" || "r") {
&rmlinks;
} else {exit 0;
}
EOT
if ((($answer eq 'add') or 'a')) {
    &addlinks;
}
elsif ((($answer eq 'remove') or 'r')) {
    &rmlinks;
}
else {
    exit(0);
}
- syntax OK

[download]

In the explicitly parenthesized version you can see exactly what your comparisons really mean to Perl.

The cake is a lie.
The cake is a lie.
The cake is a lie.

In reply to Re: Subroutines within if statements by Fletch
in thread Subroutines within if statements by muizelaar

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.