On 30 December 2011 18:54, Timothy Baldridge <tbaldri...@gmail.com> wrote: >> I think it might be more useful if freeze/thaw worked on the same >> domain as read/pr by default. That way I can swap in and out different >> serialization functions without altering the behaviour of the >> application. > > Well, from my view, read-string/print-str is completely broken when it > comes to refs: > > user=>(read-string (print-str (atom "foo"))) > RuntimeException Unreadable form clojure.lang.Util.runtimeException > (Util.java:156)
See, I kinda think that's exactly the behaviour it should have: if you cannot serialize something, then throw an exception. However, apart from that, deep-freeze looks like a really good library, and does almost everything right. I'm just nit-picking over a few details. - James -- 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