search

mzijlstra / flowcharts

Flowcharts: Computational Thinking Tool
Apache License 2.0
2 stars 0 forks source link

Standardize Side Effects #28

Closed mzijlstra closed 7 years ago

mzijlstra commented 9 years ago

Currently the call element has limited support for side effects -- it would be good to put this support into all elements that have expressions

mzijlstra commented 9 years ago

Realized that eval should return an object with the result values, and the current (possibly affected) values of the variables.

Shouldn't be too hard to implement, and then will provide support for side effects across the board, regardless of where the variable is inside the expression.

mzijlstra commented 7 years ago

Updated eval, instead of returning an object with result values the code inside eval checks if the current state is not running, and then reaches into the stack and updates the values with newer ones