If it works with Java, then it should be possible to get it working with Clojure, no? It may take some work, but should be possible.
I have to say, my experience with JSwat was adequate. Obviously a debugger that could step back would be better, but with JSwat I was able to step between Java code and Clojure code. This was indispensable. There's no way I could have gotten as far as I have with Terracotta without it. There are obvious places for improvement. As you mentioned, putting a breakpoint in clojure code, JSwat doesn't always catch it. I suspect this has something to do with macro expansions, but I'm just shooting from the hip here. Paul On Fri, Mar 6, 2009 at 10:46 AM, Dan <redalas...@gmail.com> wrote: > >> My dream debugger would be to pause execution on a certain line, be >> able to step through function calls, and have a REPL with all local >> vars available so I could explore the problem. But I'm pretty sure >> that doesn't exist. > > My dream debugger would be this: > > http://www.lambdacs.com/debugger/ > > but for clojure. In a nutshell, it instruments your java program and > record everything it does. So you don't have to pause, you can step > forward or backward through the execution, search, etc. It's a great > way to deal with mutability too because if for instance, you use > random values then they would be different every time you run your > program and some might cause crashes and others not. However, if you > recorded their values and the bug they caused, then it can't get away. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
