This repository has been archived by the owner on Nov 14, 2020. It is now read-only.

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

Closed

quoll opened this issue Dec 6, 2013 · 1 comment

Milestone

Collaborator

quoll commented Dec 6, 2013

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.

Owner

alandipert commented Dec 18, 2013

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

alandipert closed this as completed

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.