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
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?
-
