On 23 September 2010 09:31, Bruno Unna <span dir="ltr"><<a href="mailto:bruno.unna@gmail.com">bruno.unna@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">FWIW: in Perl, there are both operators as well (|| and 'or'). However, they are *not* exactly the same. Although they can be used in any context to render a boolean expression, their priority makes the difference. Taken from official documentation (<a href="http://bit.ly/dgw4GT" target="_blank">http://bit.ly/dgw4GT</a>):<div>
<br></div></div></blockquote><div><br>Low precedence "and", "or", "xor" were introduced to permit "Perl poetry", or, more seriously, to<br>permit control flow using a logical expression, especially after function calls without parentheses. <br>
see Naples or die; # same as: see(Napes) || die(); but not: see(Naples || die() );<br><br>No way this makes any sense in Drools.<br><br>-W<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div></div><div><blockquote type="cite">Binary "or" returns the logical disjunction of the two surrounding
expressions. It's equivalent to || except for the very low precedence.
This makes it useful for control flow.</blockquote></div><div><br></div><div>Nonetheless, it must be taken into account that the distinction makes sense for a Perl programmer. For a rules-writing guy (or girl) perhaps the distinction is extremely obscure.</div>
<div><br></div><div>Regards.<br><div><br></div><br></div></div></blockquote></div><br>