News for hackers. Stuff that matters.
Re:Clojure's Default Reader is Unsafe by matthavener on Friday March 08, 2013 @10:29AM (#5343912)

  ;; 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.
Re:Clojure's Default Reader is Unsafe by fogus on Friday March 08, 2013 @11:39AM (#5344323)
So you wouldn't want to use the reader if safety is needed. Instead you would use the EDN data functions.

http://clojure.github.com/clojure/#clojure.edn