On 25 July 2015 at 15:50, crocket <crockabisc...@gmail.com> wrote: > Logging libraries seem to rely on a global config. This looks like a > dangerous state that could blow up. > I researched a little, and there seems to be reader monad and dependency > injection, all of which feel awkard. > > Is there not a decent approach to passing log config without a global var? >
One way to think of logging is that it's a way of monitoring a running process. In an ideal world, we could simply log every memory interaction a process makes, and then analyse that log to discover how the process is performing. In practice that's infeasible, but it does provide a clue as to how we should think about logging. Consider logging as a way of manually marking points of interest in an application. From this point of view it makes sense that these markers should be global in scope, for the same reason that vars are. However, I do think that we should separate how we monitor out code from how those logs are actually outputted. I've been working on some ideas along those lines, but nothing I'm entirely happy with, yet. - James -- 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.
