Operator precedence is the cause of this. || has much higher precedence than 'or' does. Consider the following:

#!perl -l sub foo { print "Foo!"; return "foo"; } my $barbar=0 || foo(); print $barbar; print "---"; my $or =0 or foo(); print $or; __END__ Foo! foo --- Foo! 0

What this shows is that $var = $x || $y; is handled as $var=($x || $y); and $var = $x or $y; is handled as ($var=$x) or $y; which is actually a logical operator used as flow control and as such is pretty well equivelent to unless ($var=$x) { $y }. Where this gets interesting is that its a lot nicer to write open my $fh,$mode,$file or die "$file:$!" than it is to write my $fh; unless (open $fh,$mode,$file) { die "$file:$!" }

---
demerphq


In reply to Re: '||' vs 'or' with subroutines by demerphq
in thread '||' vs 'or' with subroutines by sweetblood

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.