Jim <jimpil1...@gmail.com> writes: > On 16/05/13 12:45, Phillip Lord wrote: >> I have a process that >> produces logging output, and I want the user to be able to define >> where that output goes. > > or you can define a multi-method or a tiny protocol with 2-3 > implementations (for GUI, raw-text or file-output) and let your user select > what he needs and potentially extend the functionality...why does this have to > be a statefull call? dynamic scope should be treated with care.... > > Jim > > ps: multi-methods allow for :default implementation which sounds to me like it > would suit your needs...
And which is the right default to pick? This is the problem. On my big screen, the GUI is okay. On my netbook, it's a pain. On travis, running headless, I want /dev/null. I could use a multi-method, but then it would have to dispatch on the basis of some thing stateful; back to square one. I think I have a solution, now, though. Still not convinced that clojure.core has got this right. But, I can move forward and, thanks to this discussion, I don't think I have missed anything obvious. Phil -- -- 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/groups/opt_out.
