I don't like debugging with printf, although Medic does seem cool.
I like to turn errors into test cases and then trace the execution of
the program and turn one test case into more. This is a nice way to
debug because it ensures the same error won't come up again.
Jay
On Sat, Feb 28, 2015 at 2:
Having spent a bunch of time writing Python over the last year (while
building Pycket [1]), the debugger is the one thing I wish I had in
Racket. This isn't because it interacts with C (I've not used any C
extensions), but because it makes debugging much faster than when I
have to use printf (my us
I think we don't miss a conventional debugger in Racket (Emacs or Dr)
because, unlike say Python, Racket is not a shallow layer over some
unsafe amalgam of C and C++. Sure there is some of it left but our
crashes don't leave core dumps because most of them are safe.
I agree that on occasion it w
On 28/02/2015 16:33, Greg Hendershott wrote:
Sure, I hardly ever want a debugger for Racket, in the way I used one
heavily and religiously for C/C++ (to step through new code the first
time instead of just hitting Run). After all we have the REPL, and
functions. And TBH printfs usually suffice.
> Don't make me want to go back to programming Racket in Emacs :-)
> But thanks for mapping Emacs back into the fold. -- Matthias
The more I do with racket-mode, the deeper my appreciation for
everything that DrRacket does. It's really quite amazing.
Also the more I program in Emacs Lisp, the mo
Don't make me want to go back to programming Racket in Emacs :-)
But thanks for mapping Emacs back into the fold. -- Matthias
On Feb 24, 2015, at 5:02 PM, Greg Hendershott wrote:
> Just a heads-up on some progress with racket-mode over the last couple
> months:
>
> - Support for errortrace
On 24/02/2015 23:02, Greg Hendershott wrote:
Just a heads-up on some progress with racket-mode over the last couple
months:
...
If you have really detailed questions, or problem reports, it would
probably be better for this list (and easier for me to track them)
if you lob them to GitHub Issu
Just a heads-up on some progress with racket-mode over the last couple
months:
- Support for errortrace in error message stack traces.
- A profile command that shows profile results in a major mode buffer
and lets you view the source locations in the other window. You can
also evaluate more e
8 matches
Mail list logo
