James: For sure. To be honest, I haven’t really thought too much about best practices. The code just naturally evolved in this way. Let me have a think about this over the weekend and come up with something.
Lawrence: I see what you are saying… and again, I need some time to think about the implications. It’s interesting for me to be able look at this in hindsight and really question the value of why I did this in a certain way.. As context, I didn’t start with the pattern and tried to fit things to it… I wrote a code bunch of code, refactored it a couple of times, and found commonalities in design that I was able to extract into what is now being discussed. So it’s really a case of tomaYtos, toMAAtos - a question of taste - and I think we are really lucky that clojure allows for all types =) >>> -- 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.
