json.lua VS ulisp

One option might be to look at the Path of Building “Data” folder. If you need them in another format (e.g. json), it wouldn’t be that hard to write a Lua script to export them in your preferred format (using this json library, for example.

If you don't want to reinvent the wheels, you might want a json encoder to transform data into strings and back. Or bitser if you want better performance and smaller files in exchange for human-readability.

Honestly, I just went with JSON because there's a nice Lua library for it (thank you https://github.com/rxi/json.lua).

I haven't thought about the file format much so far, just the experience of writing in it as if it's the "ground truth". We all seldom open our text files in a hex editor.

JSON https://github.com/rxi/json.lua

Get json.lua from here. Put it in your project directory alongside file1.lua.

Good point. How about this? It allows you to encode/decode Lua values into/from JSON.

I like this json library and tend to use it for save files (also makes them easy to edit by hand while debugging). It gets angry if you use tables with a mix of string and numerical keys, but I'd advise against that anyway. I've also used binser, which is also effective and easy to use.

lua json module can be found from here: https://github.com/rxi/json.lua

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.