fe

This is incredible. I'll be tinkering with this for a while, guaranteed. As the advantages of combining Lisp and Forth in this way are slowly revealed to me it's like unlocking parts of my brain to interact with each other that never have done before. Pretentiousness on my part aside, this is a pretty mind-blowing concept. The interpreter being in less than 1000 lines of (comprehensible) C is all the more commendable (most of these minimal languages turn out to be some monolithic Rust thing or similar, which kinda defeats the entire purpose imo). Excited to take a closer look at the source to see how the various data structures etc. are laid out in memory. I won't be able to resist making comparisons to my current/other favourite mini-language 'fe' (https://github.com/rxi/fe), a sub-1000-line Lisp also written in C. If you haven't seen th

I was wondering what the goal of the project is. The README is not very clear on it, but the implementation document [1] does state design goals: - Small memory usage within a fixed-sized memory region — no mallocs - Practical for small scripts (extension scripts, config files) - Concise source — less than 1000 loc - Portable ANSI C (Windows, Linux, DOS — 32 and 64bit) - Simple and easy to understand source - Simple and easy to use C API [1] https://github.com/rxi/fe/blob/master/doc/impl.md

Very cool! Quite similar to fe [1], a tiny, embeddable Lisp by the magnificent rxi. Seriously, if you like games and gorgeous C and Lua code, check out his projects and the games on itch.io! [1] https://github.com/rxi/fe

> Why does Fe exist. Reply to one of the GitHub issues discusses it some[1]. >> What was the motivation to create fe if you already made aria? > The same motivations I had writing aria: for the fun of programming it; trying to make something terse but still practical. Every line of code has a weight to it with consideration that would be unreasonable outside this kind of project: a project that exists just to exist. Each time you write something it becomes — or at least should become — more clear and more concise than the previous time, and if you repeat this, the original version is by comparison an over-engineered bloated mess. fe is a sequel to aria, and as such ended up smaller, simpler and faster [1]: https://github.com/rxi/fe/issues/3