Same in Perl, hence the good old pattern:
reply open my $fh, '<', 'input.txt' or die;yes, ruby inherited this from perl, though 'or' has lower precedence than 'and' in perl, and they're equal in ruby. Which sounds like something going to cause mistakes, but I yet to see 'and' and 'or' together in the same expression in ruby.
replyI've always found it odd that and/or in Ruby isn't just considered equal to &&/||, and I have never really used the english operators except for the usual modifiers like if and unless.
replyWhat is a practical use case where the lower precedence makes sense?
Those two behave in the same way if you drop the parentheses:
reply1. statement if (condition || something)
2. (statement if condition) or something