tinylisp VS ulisp

LISP has a very simple and consistent syntax, so much so that a basic interpreter can be done in only 99 lines of C.

I needed a scripting language for an old-school Sierra On-Line adventure game engine I'm working on and was looking at learning writing simple compilers / interpreters, when I stumbled across tinylisp and realized it was exactly what I needed.

Tinylisp can be a good starting point. The writeup explains how it works and how to add more features.

I've been on a bit of a retro-coding binge lately, using SDL2 for screen, I/O, and audio. For one project I replicated an NES-style sprite engine and a phase-modulated synthesizer for audio, but right now I'm currently porting tinylisp over to C++ for use in an old-school Sierra-style adventure game engine as the scripting language.

Lately, we run Robert van Engelen's 1k Lisp on ESP32 and 8266 boards: https://github.com/Robert-van-Engelen/lisp but we started on his tiny Lisp: https://github.com/Robert-van-Engelen/tinylisp (which is 99 lines of C)

I love his projects too. He's also the creator of uLisp.

http://www.ulisp.com/

Not CL, but there is ulisp (http://www.ulisp.com/) for microcontrollers, supposed to be really tiny, and there is Carp (https://github.com/carp-lang/Carp) which is without a GC so seems suitable for real-time stuff.

There's also ulisp (for Arduino projects etc.): http://www.ulisp.com/

This is larger, because there are functions for accessing peripherals, and the core is more standard lispy with 'caadr' et.al., and it has a compacting GC, so images can be saved as a compact blob.

You might consider uLisp, it's very Common Lispy for the memory constraints given (sans macros and splicing quote). And you can still connect to it and save an image. I've tried it and it works well enough. Here is the homepage.

Agreed - the interactivity is good. Lisp is close (have you seen http://www.ulisp.com/ - I can't believe they got into into that small a target!). Python is ok, but for some reason I don't use the REPL in the same way I do in Forth - I think calling functions is just harder somehow. Mostly is exploring valves from the Python REPL.