Pavel Smerk wrote:
> OMG!
> 
> Why the and and or operators have the same priority? Unlike && and || 
> and also unlike the most of, or maybe all, other languages and conventions?
Good question.

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?

-- 
Alex