Wren is an interpreter intended for use in constrained-RAM environments.
Wren's RAM requirement is under 4 KB, and it supports up to 64 KB.
-
Edit the configuration defs at the top of wren.c and in wren.h
-
make
-
./test/check-examples
-
./build (This makes a stripped executable optimized for size.)
-
./benchmark Notice how much faster it is than Python! Gee whiz.
-
Look over the examples file to get an idea what you can do. (It was mainly written as a basic test suite though.)
-
Look over (Darius's) TODO to see all the stuff not done.
-
Look over (Doug's) e_notes.txt for bugs and planned tasks.
One thing that's probably not obvious is that you can define arrays or other dynamic data structures in a Wren program. The thing is, you have to use peek (refb, refx, refv) and poke (setb, setx, setv). But you can allocate the space for it so the interpreter doesn't step all over it, by incrementing the 'cp' variable (short for compiler_ptr, its name at the C level). Same basic idea as ALLOT in Forth: get the current value of cp as the starting address for your data structure, then increment cp by its size.
Have fun!
Todd's NOTES explain the Wren Grammar and some interpreter features.
See LICENSE file for software license, and the end of release_notes.txt for credits.
The test/check-examples assumes 64-bit values.
Some of the examples, such as boot.wren and disasm.wren are written assuming a little-endian machine. This should be fixed soon.