That's interesting, thanks for your investigation! Then such decision was clearly made because Java is not the only JVM language, just as Luc said. For example, JRuby has its own class which wraps false: http://jruby.org/apidocs/org/jruby/RubyBoolean.False.html Obviously, it's impossible to implement checks like you made for each and every jvm language, so the current behaviour is totally reasonable.
It'd be cool if detailed description of this issue and rationale for that was posted somewhere, so the community could just point to it if the question will arise again. http://stackoverflow.com/questions/2020570/common-programming-mistakes-for-clojure-developers-to-avoid was a good start, but it was closed by moderators. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
