Re:Common Lisp: An Interactive Approach (1992) [pdf]
by kqr on Wednesday October 11, 2023 @02:01AM
(#37841428)
But this means you have to litter your application with support for it, doesn't it? In Common Lisp, I can stop at a breakpoint, paste in a new definition of any function in the application, and then resume and it will use the new definition everywhere rather than the one that existed when the breakpoint was triggered: https://two-wrongs.com/debugging-common-lisp-in-slime.html
[ Parent
| on HN ]
Re:Common Lisp: An Interactive Approach (1992) [pdf]
by vindarel on Wednesday October 11, 2023 @03:08AM
(#37841780)
*and not only paste, but write, in the source file, the new definition, re-compile it (C-c C-c), and resume execution from a stackframe before this call. (a clarification for folks who would think we must paste in the REPL)
That's useful not only for breakpoints but for errors. We can fix an error without re-running everything from zero. https://www.youtube.com/watch?v=jBBS4FeY7XM