;> > use zippers is probably correct. Here's a sketch I bashed out that
> >> > seems to do roughly what you want:https://gist.github.com/1807340(I
> >> > took the liberty of wrapping the whole thing in another [] under the
> >> > assumption you'd want to
/gist.github.com/1807340(I
>> > took the liberty of wrapping the whole thing in another [] under the
>> > assumption you'd want to record multiple top-level calls; if not you
>> > can just call first on the result).
>>
>> > On Feb 11, 8:39 pm, jweiss wrot
top-level calls; if not you
> > can just call first on the result).
>
> > On Feb 11, 8:39 pm, jweiss wrote:
>
> > > I've been working on a tracing library, that works much like
> > > clojure.contrib.trace (based on it, actually). One sticky problem
> > > I've
you'd want to record multiple top-level calls; if not you
> can just call first on the result).
>
> On Feb 11, 8:39 pm, jweiss wrote:
>
>
>
>
>
>
>
> > I've been working on a tracing library, that works much like
> > clojure.contrib.trace (bas
(vec (for [m stuff] (vec (butlast m
[[(+ 1 (- 5 2))] [(- 5 2)] [3] [4]]
On Feb 11, 8:39 pm, jweiss wrote:
> I've been working on a tracing library, that works much like
> clojure.contrib.trace (based on it, actually). One sticky problem
> I've found is, hierarchical logs are
ace (based on it, actually). One sticky problem
> I've found is, hierarchical logs are really crappy to try to stream to
> a file. You can't just keep writing to the end of the file - new data
> needs to be inserted before existing end-tags. So what I'm doing is
>
I've been working on a tracing library, that works much like
clojure.contrib.trace (based on it, actually). One sticky problem
I've found is, hierarchical logs are really crappy to try to stream to
a file. You can't just keep writing to the end of the file - new data
needs to be
