Unlogical ?

[Christer Nilsson]

Hmm, why are these two assertions breaking?

def test_strange
assert_equal true, true && true
assert_equal false, true && false
assert_equal false, false && true
assert_equal false, false && false

assert_equal true, true and true
assert_equal false, false and true
assert_equal false, false and false
assert_equal false, true and false # breaks

assert_equal true, true || true
assert_equal true, true || false
assert_equal true, false || true
assert_equal false, false || false

assert_equal true, true or true
assert_equal true, true or false
assert_equal false, false or false
assert_equal true, false or true # breaks
end

Christer

 

[Jeremy Kemper]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hmm, why are these two assertions breaking?

assert_equal false, true or false
assert_equal(false, true) or false
assert_equal(false, (true or false))

jeremy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iD8DBQFDmTdlAQHALep9HFYRAj6iAJ0eukjPlXB7XIobBcqQcZbQYtE7IgCfT/Ka
0gwx518M4IXNLwdG0wTvKqM=
=1CJC
-----END PGP SIGNATURE-----

 

[Logan Capaldo]

--Apple-Mail-2--958771726
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
delsp=yes;
format=flowed

assert_equal true, false or true # breaks

or has relatively low precedence. I imagine ruby sees assert_equal
(true, false) or true.
Try throwing in some parens eg. assert_equal(true, false or true)



--Apple-Mail-2--958771726--

 

[Benedikt Heinen]

Hmm, why are these two assertions breaking?

assert_equal false, true && false
assert_equal false, true and false # breaks

'&&' and 'and' have a different level of precedence, as such, the two
statements are read as:

assert_equal (false, true && false)
assert_equal (false, true) and false


Similar for the 'or'. In the case of the or, you could even observe this
in irb:

irb(main):004:0> puts false || true
true
=> nil
irb(main):005:0> puts false or true
false
=> true


Since the 'or' has a lower precedence than the '||', the 'or' is applied
to the result of puts, not to the parameter 'false'.




Benedikt


ALLIANCE, n. In international politics, the union of two thieves who
have their hands so deeply inserted in each other's pockets that
they cannot separately plunder a third.
(Ambrose Bierce, The Devil's Dictionary)

 

[Christer Nilsson]

assert_equal (false, true && false)
assert_equal (false, true) and false

Pickaxe does not list "," in the operator precedence table.

<snip from pickaxe>
&&
||
.. ...
? :
= etc
<<= etc
defined?
not
or and
</snip from pickaxe>

The only operator relating to "," here is "=".
Maybe it has to do with parallell assignment, as the comma is used
there.

a, b = false, true

My workaround will be to use "&&"

Christer

 

[daz]

Maybe it has to do with parallell assignment, as the comma is used
there.

I don't think it's that.

My workaround will be to use "&&"

Parens will work around either.


&&, || "give" you parenthesised left and right terms -
and, or don't.

a && b equates with: (a and b)

r = true and false
equates with:
((r = true) and false)

Test:
r2 = ((r = true) and false)

p [r, r2] #=> [true, false]


The following won't make anything clearer but it
may help you to understand why it's not clear

r = true and false ; p r #=> true
r = true and (false) ; p r #=> true
r = (true ) and false ; p r #=> true
r = true && false ; p r #=> false
r = ( true and false ) ; p r #=> false
r = ( true and (false)) ; p r #=> false
r = ((true ) and false ) ; p r #=> false
puts
r = false or true ; p r #=> false
r = false or (true ) ; p r #=> false
r = (false) or true ; p r #=> false
r = false || true ; p r #=> true
r = ( false or true ) ; p r #=> true
r = ( false or (true )) ; p r #=> true
r = ((false) or true ) ; p r #=> true


daz

 

[gwtmp01]

Pickaxe does not list "," in the operator precedence table.

Because ',' is not an operator. It is an argument separator.

is the same as:

assert_equal(false,true) and false

I think the space between the method name and the opening
paren of the argument list is confusing you.

Gary Wright