@johnsondavies, hi, take a look at this commit where I implemented
errors. Because uLisp doesn’t have multiple return values, I made
nothing when an error occurs within.
Also it’d be great if the special forms would signal error in all cases of malformed forms instead of failing/accessing invalid memory:
(dotimes ()) ((lambda)) (let) (let*) (with-output-to-string)
and so on.
Perhaps, I could look into that if I find the time for that; however, contributing to this project isn’t easy, especially as you keep separate code bases for different families of boards. I understand the motivation of single ino files, well, I’ll think about this and then share my thoughts about what could be done for easier contributing and keeping different ino files in sync.