5 ms·

> you needed to restart your program after changing the code Wow. No. This is a really basic debugging feature that's been around for over a decade. You can al

by NavinF 4y ago

> you needed to restart your program after changing the code Wow. No. This is a really basic debugging feature that's been around for over a decade. You can also drag-and-drop the instruction pointer to another line, watch and change variables in real time, etc. I swear, every LISP-related thread has someone touting ancient features as if they are somehow new or unique.

medo-bear 4y ago
whats your etc.? in common lisp i can pretty much redefine the WHOLE compiled program at runtime. boasting about redifining variables to someone using lisp is a big LOL moment. as far as interactivity and debugging is concerned, besides smalltalk, its not nearly as good in any other language as it is in common lisp
- NavinF 4y ago
  Very cool, that's definitely not a common feature in every other debugger /s
  - lispm 4y ago
    Your C++ debugger let's you redefine an arbitrary C++ class in a running program and the existing program and data is changed. /s
  - imaltont 4y ago
    I don't think you know just how modular a Common Lisp environment is. Sure there is some hot reloading that sometimes works and you can change the value of variables, maybe even jump back and forth in your stack trace. Rarely does it do any of them as well as Common Lisp though, where the only thing that doesn't dynamically update when you change something is struct-instances and macros. Functions, variables/values, classes (including instances) can all change as you want it without restarting anything. When something goes wrong, like errors or exceptions, you can modify some code, restart some where on the stack, ignore it and continue execution, insert dummy value or insert a placeholder function. Some form of interactivity with the debugger is common in my experience. The level of interactivity you get with Common Lisp is not.
  - deleted 4y ago
    [deleted]
  - medo-bear 4y ago
    it's not :)
deleted 4y ago
[deleted]

by NavinF 4y ago

medo-bear 4y ago

whats your etc.? in common lisp i can pretty much redefine the WHOLE compiled program at runtime. boasting about redifining variables to someone using lisp is a big LOL moment. as far as interactivity and debugging is concerned, besides smalltalk, its not nearly as good in any other language as it is in common lisp

NavinF 4y ago
Very cool, that's definitely not a common feature in every other debugger /s
- lispm 4y ago
  Your C++ debugger let's you redefine an arbitrary C++ class in a running program and the existing program and data is changed. /s
- imaltont 4y ago
  I don't think you know just how modular a Common Lisp environment is. Sure there is some hot reloading that sometimes works and you can change the value of variables, maybe even jump back and forth in your stack trace. Rarely does it do any of them as well as Common Lisp though, where the only thing that doesn't dynamically update when you change something is struct-instances and macros. Functions, variables/values, classes (including instances) can all change as you want it without restarting anything. When something goes wrong, like errors or exceptions, you can modify some code, restart some where on the stack, ignore it and continue execution, insert dummy value or insert a placeholder function. Some form of interactivity with the debugger is common in my experience. The level of interactivity you get with Common Lisp is not.
- deleted 4y ago
  [deleted]
- medo-bear 4y ago
  it's not :)

deleted 4y ago

[deleted]