When falsely using a colon ':' at the end of an expression in an scvd file, like in this example:
TestBit1=(TestVariable>>1)&0x1:
There is no direct hint for this type of error in the debug log when inspecting the output for executing this expression. What you get is:
[debug] Line: 9: Completed executing <calc>, TestBit1=(TestVariable>>1)&0x1:, value: undefined
One can speculate what "undefined" means in this case.
A closer look at the generated debug output shows a single error message at the beginning of the output:
[error] [Line: 9 Tag: calc ] Expression AST is undefined for expression: TestBit1=(TestVariable>>1)&0x1:
But the expression can be executed x-times, while the current error is only printed once at the start of the output. This way, the error could be missed.
So it could probably help if some error could also be printed during the execution of such an expression, where probably one normally looks at to analyze an issue.
Attached is the Test_Case.scvd for reference.
Test_Case.scvd.txt
When falsely using a colon ':' at the end of an expression in an scvd file, like in this example:
TestBit1=(TestVariable>>1)&0x1:There is no direct hint for this type of error in the debug log when inspecting the output for executing this expression. What you get is:
[debug] Line: 9: Completed executing <calc>, TestBit1=(TestVariable>>1)&0x1:, value: undefinedOne can speculate what "undefined" means in this case.
A closer look at the generated debug output shows a single error message at the beginning of the output:
[error] [Line: 9 Tag: calc ] Expression AST is undefined for expression: TestBit1=(TestVariable>>1)&0x1:But the expression can be executed x-times, while the current error is only printed once at the start of the output. This way, the error could be missed.
So it could probably help if some error could also be printed during the execution of such an expression, where probably one normally looks at to analyze an issue.
Attached is the Test_Case.scvd for reference.
Test_Case.scvd.txt