And and or priority

Ruby
21

Elliot T. wrote:

irb(main):001:0> true and false or true and false
=> false

tells me that and binds tighter than or, unless something unobvious is
going on, which might well be…

Have you got a counterexample handy?

irb(main):008:0> true or true and false
=> false

Good counter-example :slight_smile: Now I understand. It seems to be evaluated in
terms of the first encountered. Unless… that’s wrong too? :slight_smile: