Use abstractions, forget inheritance. Try modeling what the program does in terms of data conversion. Then you will only need functions and data.
On Saturday, November 17, 2012 2:40:05 PM UTC+1, Jonathon McKitrick wrote: > > One project I've considered porting is highly OO, with a large number of > classes and several levels of inheritance. In Common Lisp, I'd just use > CLOS. What methodology would be good to translate such a project to > clojure, while maintaining heavy reuse of inherited behavior and > abstraction? -- 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
