Rich: > On Sep 6, 2012, at 9:10 PM, Weber, Martin S wrote: > > which problem other than "NIH" is edn solving? - given it's a subset of > > clojure's data notation, it's not really native clojure either, so you > > gotta convert to/fro. > Of course it's native Clojure. Being a subset doesn't affect that. Clojure > can read/print it without conversion.
Of course. For some data.But "subset" means there is clojure data that it cannot represent. Thus even though the data that it can represent will not have to be converted, the data it cannot, will have to be. To determine which data can or can not be represented, each piece of data must be tested for whether or not it lies in this subset. Which means that you cannot blindly write out any clojure data. Then you read it and will want to reconstruct your representation of that data that did not lie in the subset. The tagged literals might completely take care of that. But this is not the same level of nativeness than printing out an integer and reading it back in. If you're going to establish a new alternative, why not go for the whole cake. I assume this question will be answered by the rationale. > > So: Why do we need another JSON? > > > > I'm sure you have answers to these questions, possibly answered them > > before, but definitely not answered them on the edn page. > > > Correct, there isn't yet a rationale on that page. Coming soon. Looking forward to that. Regards, -Martin -- 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
