News for hackers. Stuff that matters.
Re:REPL Debugging: No Stacktrace Required (2017) by jedberg on Monday March 09, 2020 @06:05AM (#22524205)
Fun REPL story: Reddit was originally written in LISP, so you could also manipulate the live running code with the REPL.

Sometimes Steve would do that to add a new feature or change some broken code.

The danger was that if you didn’t copy/paste the fix back to the saved source, the problem would return when the app restarted!

Re:REPL Debugging: No Stacktrace Required (2017) by eadmund on Monday March 09, 2020 @07:14AM (#22524469)
It'd be pretty simple — albeit so very much a bad idea — to run the REPL from a stream which saved everything typed in the REPL to a log read in at startup. A fancier version might allow log editing. A really fancy version might save everything to a log and offer commands to view expressions in the log & copy the desired ones to the startup file, or another file.

Or one could just remember to move corrected source back to the right place.

This is probably somewhere where a Smalltalk image-based browser would be preferable — it would/could unify the REPL and editing source.

Re:REPL Debugging: No Stacktrace Required (2017) by lispm on Monday March 09, 2020 @07:24AM (#22524516)
You would drive the REPL from the editor. Change the code in the editor and evaluate into the REPL. Still you need to try out if the error in a fresh build is still fixed after that.
Re:REPL Debugging: No Stacktrace Required (2017) by agumonkey on Monday March 09, 2020 @08:37AM (#22524863)
what lisp did they use ? SBCL ? also I believe lisps have image patch storing facilities..