Refactoring for reuse is a kind of early optimization? Agreed! Generally for me it waits until the second or third rewrite, as by then I have a bit of an idea about where I am headed with the code.
OTOH, I finally realized that when I don't know where I am going with something, keeping the logic in functions instead of methods is probably safest. I'm thinking now that methods should mostly just be used for their polymorphism as just a very thin layer over a set of interfaces. I was so impressed with the advantages of Java over C++ when I started using it 20 years ago. But now that I've been exposed to Clojure, I'm inclined to minimize my use of OO and use objects mostly as what I used before OO: dispatch tables! -- 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/d/optout.
