>> On the other hand, defrecord/deftype encourage you to write your protocol >> implementation in a way that cannot be reused unless you very specifically >> plan for it (factoring the protocol implementation into a separate map) and >> use a coding style that (might?) be less efficient (i.e., adding the >> protocol implementation via extend rather than directly in defrecord). This >> is not so good and potentially limits the value of protocols for developing >> complex systems. >
Inheritance is bad because it ties code reuse to a (mostly) non-significant hierarchy. That is not a reason to prevent all code reuse from deftypes. (It is not because OO gets it wrong that we should not try) -- 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
