> 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) deep-freeze attempts to make all data structures round-trip for uses of writing to disk, writing to the network, etc. Making deep-freeze behave like read-string/print-str is not really the goal here. If, at some point, Clojure re-writes it's read/print functions to round-trip, then we could look at better compatibility. I'm open to suggestions here, but simply spitting out "#<Atom@10987197: foo>" is not an acceptable answer. Timothy -- 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
