Hi James! I'll be the first to admit that I do not yet have a strong case here. And yeah, it looks like I'm introducing some boilerplate myself to do things this way. Which probably just means that I need to learn how to write macros or some such. :-)
I was just saying that the calf and yearling databases both do file io and I was going to have more of the same in the heifer database. So my duplicate code argument was a bit bogus, as in-line code is always cleaner and faster. I am looking now at instance mixins for atoms and channels. Should be an interesting experiment. Calf and yearling both are based on an atom and I need to switch to channels in heifer as I want to pipeline the transaction log. So I am thinking of first writing an atom mixin, then reworking calf and yearling to use it, and then replacing the atom mixin with a channel mixin. Instance composition gone crazy. :D -- 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.
