My thought would be to drop exceptions from normal logging calls. 1) It wont *break* any code, it may change the log output slightly as the exception is rendered by str or format instead of by the java logging formatter.
2) I think this is least surprising. 3) The exception taking java call could be expose as logex. 4) For logs, toString on the exception rarely enough though. I get the feeling that exceptions in the normal log arg list still need to be treated specially when converting to a string such that the stack trace is captured. But I think this special treatment should not be arity dependent, ie: (log "OMG, foo was " foo ", it should never be!" exception "What should I do?") should not behave differently from (log "OMG" exception). I guess there are two options here: Use special stringification of exceptions, or leave it to the user to use logex or similar if they want full exception details. 5) I expect the configurable java formatting rules that most people care about are line breaks and stamping, not the string contents. Note that the object list taking call is not exposed, and nobody has been asking for that - it seems quite undesirable to be wrangling java log formatting like this from inside Clojure. The exception string contents is important however. Regards, Tim.
-- 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
