On Tue, Feb 11, 2014 at 7:32 AM, Phillip Lord <phillip.l...@newcastle.ac.uk>wrote:
> "John D. Hume" <duelin.mark...@gmail.com> writes: > > Other than the new (and quite minimal) Java API for calling > > Clojure code[1], the details of Clojure's underlying Java classes are > > considered implementation details and could change from release to > release > > without being considered a breaking change. > > > And the interfaces? I mean, ISeq is defines the sequence abstraction. When I said "underlying java classes" I meant "underlying Java classes and interfaces." Although there are contrib and third party libraries that depend on these implementation details, I think the message to the community at large has always been not to depend on them, and as far as I know, the maintainers have not committed to keeping anything other than the newly documented Java API and the existing Clojure API in Clojure stable. So if I'm not mistaken, in spite of the fact that you can find many examples of people doing it, there is no blessed way to create custom Clojure data structures (unless you count defrecord) and no official documentation to encourage or assist you. Hopefully I am mistaken, or this will change someday soon. :) -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
