Re:How to Write a (Lisp) Interpreter (In Python) (2010)
by housecarpenter on Monday March 11, 2024 @08:46AM
(#39667503)
I haven't used CL myself, but it wouldn't surprise me if CL does a better job. Just pointing out that Python is significantly better in this respect than it used to be. In particular, using VS Code with Pylance, I can see type errors highlighted as soon as I write the code---I don't even need to use a keystroke. 24 years ago, I don't think anything like that was possible; the language didn't even support type annotations.
Re:How to Write a (Lisp) Interpreter (In Python) (2010)
by llm_trw on Monday March 11, 2024 @08:48AM
(#39667536)
It's pretty much impossible to explain to people what it's like to work in a CL environment.
A good presentation on what we're missing: https://www.youtube.com/watch?v=8Ab3ArE8W3s
Re:How to Write a (Lisp) Interpreter (In Python) (2010)
by zarathustreal on Monday March 11, 2024 @08:57AM
(#39667633)
If you’re part of the group missing something, how would you know?
Re:How to Write a (Lisp) Interpreter (In Python) (2010)
by llm_trw on Monday March 11, 2024 @08:59AM
(#39667655)
I use python/C for my day job and common lisp for my wacky off the clock hacking.
I used to use scheme and racket but the joy of debugging in CL is worth putting up with two (or four) name spaces.
And there's also been improvement, see Coalton for a ML on top of CL. (https://github.com/coalton-lang/coalton/) (and SBCL itself evolves)