Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-10 Thread Phil Hagelberg
Tassilo Horn writes: > I fixed the definition directly in the swank-clojure-1.3.4.jar and then > wanted to write a patch against clj-stacktrace's git master branch. As > it turns out, it's already fixed in there. Funnily, it was Phil himself > who committed that patch written by Michael van Ack

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-10 Thread Baishampayan Ghose
> I fixed the definition directly in the swank-clojure-1.3.4.jar and then > wanted to write a patch against clj-stacktrace's git master branch.  As > it turns out, it's already fixed in there.  Funnily, it was Phil himself > who committed that patch written by Michael van Acken. > > Phil, maybe you

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-10 Thread Tassilo Horn
Tassilo Horn writes: Hi again, > Maybe the problem is that clj-stacktrace stumbles upon those names? > > But on the other hand: since *e contains the last exception and that > is the divide by zero exception and not some exception from > clj-stacktrace, this doesn't seem very likely... Debuggin

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-10 Thread Tassilo Horn
David Nolen writes: Hi David, > Do you see the same issue when working with lazy sequences? We > definitely don't eat exceptions. No, exceptions in lazy sequences show up fine. (defn blow-up [i] (map #(/ 1 %) (iterate inc i))) (take 200 (blow-up -100)) ;Divide by zero ; [Thrown c

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-09 Thread David Nolen
Do you see the same issue when working with lazy sequences? We definitely don't eat exceptions. On Monday, January 9, 2012, Tassilo Horn wrote: > Phil Hagelberg writes: > > Hi Phil, > >>> One thing that really made the programming extremely hard was that I >>> don't get any backtraces if an exce

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-09 Thread Tassilo Horn
Phil Hagelberg writes: Hi Phil, >> One thing that really made the programming extremely hard was that I >> don't get any backtraces if an exception occurs inside a `run'. For >> example, I get this in SLIME with M-x clojure-jack-in RET. > >> (defn wrongo [a b] false) ;; intentionally

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-09 Thread Phil Hagelberg
Tassilo Horn writes: > One thing that really made the programming extremely hard was that I > don't get any backtraces if an exception occurs inside a `run'. For > example, I get this in SLIME with M-x clojure-jack-in RET. > (defn wrongo [a b] false) ;; intentionally broken > ;=> #'

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-06 Thread Mark
Great! Thanks -- 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

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-06 Thread Tassilo Horn
Mark writes: Hi Mark, > I'm very interested in using core.logic to query a relational database > or other data store. I figure querying custom java objects is a good > example of how to tackle this problem. > > Would you mind posting your code somewhere? I want to write a blog posting about it

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-06 Thread Tassilo Horn
Phil Hagelberg writes: Hi Phil, >> (run* [q] (wrongo 1 2)) >> ; ClassCastException java.lang.Boolean cannot be cast to >> ; clojure.lang.IFn clojure.core.logic.Substitutions (logic.clj:207) >> >> But where is my backtrace? > > The Clojure REPL has actually never provided stack traces for

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-06 Thread Phil Hagelberg
Tassilo Horn writes: > The "; Evaluation aborted." instantly appears. No backtrace, no error > message, not even in the *swank* buffer. > > If I use a plain "lein repl" instead, I get at least an error message: > > (run* [q] (wrongo 1 2)) > ; ClassCastException java.lang.Boolean cannot be ca

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-06 Thread Mark
I'm very interested in using core.logic to query a relational database or other data store. I figure querying custom java objects is a good example of how to tackle this problem. Would you mind posting your code somewhere? -- You received this message because you are subscribed to the Google

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-06 Thread Tassilo Horn
Anthony Grimes writes: Hi Anthony, > The last stacktrace that occurred in a REPL is bound to *e. Try > (.printStackTrace *e). That should work in the REPL. Might not in > SLIME. Yes, that does the trick. Ambrose also pointed me to (clojure.repl/pst *e) which is as good. Thanks, Tassilo -- Y

Re: core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-06 Thread Anthony Grimes
The last stacktrace that occurred in a REPL is bound to *e. Try (.printStackTrace *e). That should work in the REPL. Might not in SLIME. -- 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 Not

core.logic, leiningen, clj-stacktrace: someone eats my backtraces

2012-01-06 Thread Tassilo Horn
Hi all, I'm still playing around with core.logic and managed to define relations that allow for querying my custom java datastructures with it. Thanks a ton to Ambrose, who has helped me a lot! One thing that really made the programming extremely hard was that I don't get any backtraces if an ex