`and` is the same as `&&` but why does `and` have lower precedence?

Question

In ruby, and is the same as &&, but why does and have lower precedence?

false and false || true # => false
false && false || true # => true

Well, it's not "the same" precisely because of the lower precedence. What is your question, again? — Sergio Tulentsev, Apr 06 '16 at 08:10
Anyway, you can check Ruby operators precedence here http://stackoverflow.com/questions/21060234/ruby-operator-precedence-table — Ilya, Apr 06 '16 at 08:19

score 4 · Accepted Answer · edited Apr 06 '16 at 08:41

4

You're absolutely correct that the humanised operators have lower precedence. There is an excellent (and brief!) article on this here if you want more information.

Simplest answer (from that article):

Properly understood, and and or are control flow operators, not boolean operators.

edited Apr 06 '16 at 08:41

Jörg W Mittag

363,080
75
446
653

answered Apr 06 '16 at 08:26

Matt

13,948
6
44
68

`and` is the same as `&&` but why does `and` have lower precedence?

1 Answers1