Thank you Luc!
On Tue, Sep 27, 2011 at 11:44 PM, Luc Prefontaine
wrote:
> First shot of tools.trace is now available on github:
>
> http://github.com/clojure/tools.trace
>
> As for the traceforms macro, you will notice that when an exception is
> trapped, I recompose
> an new exception with the
Hi,
First shot of tools.trace is now available on github:
http://github.com/clojure/tools.trace
As for the traceforms macro, you will notice that when an exception is trapped,
I recompose
an new exception with the necessary form traceback information instead of using
print.
The main reason is
Fine, I merged the new version and I will add a couple of tests related to
these changes.
Luc
On Mon, 26 Sep 2011 18:46:12 +0200
Jonathan Fischer Friberg wrote:
> I looked at it today and have updated the macro.
> (same gist: https://gist.github.com/1209498)
>
> Additions:
> It detects if a f
On 26 September 2011 18:46, Jonathan Fischer Friberg
wrote:
> To Marczyk:
> Sure, where to?
Great, thanks!
The relevant details are available on this page:
http://clojure.org/contributing
There's a one-page form to print out, sign and send off to Rich by
snail mail. Once it's processed, your n
I looked at it today and have updated the macro.
(same gist: https://gist.github.com/1209498)
Additions:
It detects if a form contains (recur ...), and if it does,
the form isn't wrapped in (try ...).
trace vectors, maps, and sets.
trace (fn* ...) & (new ...)
---
The code feels a bit "thrown t
Oh, that's a nice idea! Definitely looks like a worthy addition to the
trace lib.
I believe the process around contributions to contrib involves a CA,
though; Jonathan: do you have one in place? Any chance you might be
convinced to submit one if not? :-)
Sincerely,
Michał
--
You received this m
include
> > your trace-forms
> > macro in it. Feeling ok with this ? Comments ?
> >
>
> Sounds good to me.
> After all, I sent it to this list so that others could make use of it!
>
> When it comes to issues, in 1.3 it's not allowed to recur across
> (try ...)
>
> I am moving the trace contrib stuff to 1.3. I would like to include your
> trace-forms
> macro in it. Feeling ok with this ? Comments ?
>
Sounds good to me.
After all, I sent it to this list so that others could make use of it!
When it comes to issues, in 1.3 it's not all
Hi Jonathan,
I am moving the trace contrib stuff to 1.3. I would like to include your
trace-forms
macro in it. Feeling ok with this ? Comments ?
The issues you underlined are not runtime errors, they are compilation errors.
There's not much you can do to trap these.
The macro is still val
It was tested with 1.2.1
Jonathan
On Wed, Sep 14, 2011 at 9:09 AM, Sergey Didenko wrote:
> Looks interesting. Did you use it with Clojure 1.3 or earlier?
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to c
Looks interesting. Did you use it with Clojure 1.3 or earlier?
--
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
Hello,
I made a small macro, if anyone is interested.
https://gist.github.com/1209498
It wraps one or more forms and if an exception is thrown,
prints the form that caused it, and throws the exception itself.
Examples:
user=> (trace-forms 3)
3
user=> (trace-forms (+ 6 (/ 9 0)))
java.lang.Arith
12 matches
Mail list logo
