search

alandipert / gherkin

a functional programming language and interpreter written in GNU Bash 4
https://tailrecursion.com/~alan/Lisp/GherkinHistory.html
BSD 3-Clause "New" or "Revised" License
522 stars 31 forks source link

lisp_eval to change to a stack-based state machine #31

Closed quoll closed 10 years ago

quoll commented 11 years ago

Complex jobs can lead Gherkin to segfault. This appears to be due to callstacks getting too deep.

To avoid this, we want to rewrite lisp_eval to be a large loop. Operations then update the stack and the operation state, and loop back around.

alandipert commented 10 years ago

Closing for now, dupe of #29. See #29 for further analysis and discourse.