SLExecutionStack class

Custom execution stack to mimic compilation behavior A script is composed of states, which have every event listed in SLEvents, or OSEvents which inherits SLEvents Each event will be composed of an execution stack. Custom function can be defined, they shall be stored in a dictionary with their execution stack

The execution stack should execute each function contained within in sequential order.

The execution stack cannot be altered once created, it is designed to be assembled, then executed, to change it, one must create a new stack.

Variables are defined in the SLMemoryStack. On parse, a variable will be created, then inserted into the memory stack. Naming convention is as follows. global: g_ global_function: g_f local:

Any function here will need to be parsed properly to edit the memory stack if applicable before adding it to the execution stack

NOTE: Dart does not have a JIT Compiler that can at runtime without the Dart SDK compile a dynamic dart script against the running application To make up for this, we must put in place a structure that would allow parsing the script and still allowing execution within our own codebase.