An Exploration of SBCL Internals (2020)
121–130 of 194 posts
Re: An Exploration of SBCL Internals (2020)
#122Re: An Exploration of SBCL Internals (2020)
#123Re: An Exploration of SBCL Internals (2020)
#124Re: An Exploration of SBCL Internals (2020)
#125Re: An Exploration of SBCL Internals (2020)
#126Re: An Exploration of SBCL Internals (2020)
#127Re: An Exploration of SBCL Internals (2020)
#128Re: An Exploration of SBCL Internals (2020)
#129My issue prevent me from investing in Lisp is that Erlang gives me a similar REPL which I believe, though I am not a Lisp developer, is a huge value proposition of Lisp. I utilize REPL-based development using Erlang. The macro narrative is worse in Erlang; but Lisp isn't perfect either in other ways. The point is, I net out staying on the BEAM. What I like about Lisp is that I think it's a tool that will serve you fo…
- can't install libraries from the REPL while working on your program
- can't "compile this function" with a keystroke (I did find "send region/line/buffer to REPL" which is different, or "reload module")…
- … and get type errors and warnings
- can't get an interactive debugger on an error, go to the bogus line (while keeping the debugger), fix the function, compile it, switch back to the debugger, resume execution from any point in the stack. I only found out IEx.pry which is useful and all, but looks like Python's ipdb break point.
- lack of little useful editor commands, at least in the Emacs modes I tried like "write this function in the REPL", "eval and print the last expression". I struggled to have the "go to definition" feature but that depends on the IDE I suppose. The Emacs modes are not in good shape :S
- no cross-references? doubting. And maybe other small things only about the REPL, didn't find my notes.
differences of runtimes are also at play here, but I still find it interesting to compare the REPL experience, I'll welcome more comparisons.