4 ms·

Certainly feasible: Smalltalk debuggers do this. And Smalltalkers (allegedly) use a workflow just like you describe.

• danmaz74 15y ago
  I read about this, and even tried downloading squeak once, but didn't find it very compelling. I admit that I might not have given it the time it needed, though...
  • drothlis 15y ago
    A few weeks ago I whipped up this 3-minute video showcasing a Smalltalk class browser, method finder, and debugger: http://vimeo.com/27850933 http://vimeo.com/27850933
• cwp 15y ago
  Yup. I often do something like this: - write a test for a method that isn't there yet - run it, get a red bar, as expected - run it in debug mode, and get a debugger - write the method implementation in the debugger - possibly write other methods that the new method calls, also in the debugger - resume the program, get a green bar Writing code in the debugger is great, because you've got all the runtime state right in front of you, and you can step through the code you're working on. I'd love, love, love to see this in Dart.
  • danmaz74 15y ago
    But, is it possible to step backwards from the current state of the VM, to execute a changed code?