;; especially since read-string will be fixed in clojure 1.5 so that ;; binding *read-eval* to false around it will make it safe, as far as In clojure 1.5 wi

;; especially since read-string will be fixed in clojure 1.5 so that ;; binding *read-eval* to false around it will make it safe, as far as In clojure 1.5 with read-eval bound to false, the reader is still unsafe for malicious input. Since the Clojure reader must be able to construct arbitrary Java objects via their constructors, any constructor can be called from the reader even with read-eval bound to false.