Restoring subject again
On Aug 6, 12:48 pm, Anniepoo wrote:
> Sorry for the confusion - I read this list on an email feed. Turns out
> replying to a message from there and changing the subject isn't
> sufficient to start a new thread. Apparently it renames the thread.
> (suboptimal).
>
> ori
Ah, very well. I find it useful to print out so I know which code is
doing the logging, since stack inspection is very expensive, and in
the case of clojure, looks like a mess of underscores and dollar
signs. ;)
On Aug 6, 12:31 pm, Richard Newman wrote:
> > In every case the name used by the lo
>
>
> In every case the name used by the log is the runtime *ns*, which
> really defeats the purpose of naming the specific usages of log. I'm
> surprised no one mentioned this (imo wrong) behavior.
In my case, I don't see the namespace being printed in my log entries,
so I wasn't even aware t
Ok, yes, I will blame my idiocy on sleep deprivation.
In every case the name used by the log is the runtime *ns*, which
really defeats the purpose of naming the specific usages of log. I'm
surprised no one mentioned this (imo wrong) behavior.
I'll get to work on fixing it so it behaves properly.
Restoring this thread's original subject.
On Aug 6, 10:40 am, ataggart wrote:
> Anne, please don't threadjack. Now my original subject appears
> missing, since you renamed it.
>
> On Aug 6, 1:03 am, Anne Ogborn wrote:
>
>
>
> > (use 'clojure.contrib.duck-streams)
> > (spit "C:\\test.txt"
> >
On Aug 5, 11:24 pm, Richard Newman wrote:
> > Bah! I tried to simplify the example code, and missed conveying the
> > actual problem. Your example code (and sadly, mine) pulls *ns* at
> > runtime, the logging macro doesn't; it writes the value of the *ns* at
> > macro-expansion-time precisely
> Bah! I tried to simplify the example code, and missed conveying the
> actual problem. Your example code (and sadly, mine) pulls *ns* at
> runtime, the logging macro doesn't; it writes the value of the *ns* at
> macro-expansion-time precisely so that it will be the "right" value
> when called.
On Aug 5, 9:11 pm, Richard Newman wrote:
> > In testing out clojure.contrib.logging within a generated servlet, I
> > noticed that the value of *ns* is always clojure.core, and not the ns
> > of the code.
>
> I have observed this too (running in SailFin, which is based on
> GlassFish).
>
> >
> In testing out clojure.contrib.logging within a generated servlet, I
> noticed that the value of *ns* is always clojure.core, and not the ns
> of the code.
I have observed this too (running in SailFin, which is based on
GlassFish).
> Expected response: com.example.servlet
> Actual response:
