currently the code evaluator is designed to stop descending a run-tree when it hits a non-process symbol. This works fine if PARAM_REF symbols are always direct children params of processes. But if they are hidden by a data symbol they wont get substituted in for. We can either walk the entire code tree, or require coders to mark tree portions that need walking with a special instruction.
Actually this got reversed, the code is now completely evaluated by default. The issue to address is if we don't have to, can we find a way to optimize points at which to stop.
currently the code evaluator is designed to stop descending a run-tree when it hits a non-process symbol. This works fine if PARAM_REF symbols are always direct children params of processes. But if they are hidden by a data symbol they wont get substituted in for. We can either walk the entire code tree, or require coders to mark tree portions that need walking with a special instruction.