Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

(Boolean. false) in Clojure

According to http://hyperpolyglot.org/lisp, the only falsehoods in Clojure are false and nil. Indeed, surprisingly enough, (Boolean. false) is not false:

user=> (if (Boolean. false) 1 2)
1
user=> (not (Boolean. false))
false
user=> (false? (Boolean. false))
false

On the other hand, it somehow is false:

user=> (class false)
java.lang.Boolean
user=> (= false (Boolean. false))
true

This is rather counterintuitive. Are there reasons for this behaviour or was it simply overlooked?

like image 816
zabolekar Avatar asked Sep 07 '13 19:09

zabolekar


Video Answer


1 Answers

You can find the explanation at http://clojure.org/special_forms#if.

It's good to read the whole paragraph, but here's the crucial bit excerpted, emphasis added:

[...] All [...] conditionals in Clojure are based upon the same logic, that is, nil and false constitute logical falsity, and everything else constitutes logical truth, and those meanings apply throughout. [...] Note that if does not test for arbitrary values of java.lang.Boolean, only the singular value false (Java's Boolean.FALSE), so if you are creating your own boxed Booleans make sure to use Boolean/valueOf and not the Boolean constructors.

Compare

System.out.println(Boolean.valueOf(false) ? true : false);  // false
System.out.println(new Boolean(false)     ? true : false);  // false

with

user=> (if (Boolean/valueOf false) true false)
false
user=> (if (Boolean. false) true false)
true

Thus, (Boolean. false) is neither nil nor false, just as (Object.) is neither nil nor false. And as @Chiron has pointed out, it's bad practice to use it anyway.

As for (= false (Boolean. false)) being true, I think @looby's explanation is spot on: Since = relies on Java's equals method, the special semantics of conditionals in Clojure don't apply, and boolean equality will be as it is in Java.

like image 92
glts Avatar answered Oct 08 '22 22:10

glts