Finding errors can be overwhelming when working with complex piece of code. So many statements ... tricky logic ... How is this even working? Sounds familiar right?
When you use sub functions it gets even more complex. The function can be called multiple times. Which one is the problematic one? Isn't there an easy way to find the error? Sure you can debug the code and trace the execution line by line until it stops. But why did it stop? Then you check the error message in Simulation Monitor. But did you recall the call stack? Probably not ...
Now there is a new way to detect errors directly in the SCL debugger. It simply halts the execution at the problematic statement. Just like putting a breakpoint on it. The debugger shows the error in a balloon popup like this:
Once it breaks the execution you can see the call stack and navigate it to see the path that lead to this error. Something more: You have the option to ignore the error and resume the execution or abort it. Stepping also works.
This is a new feature in Process Simulate v2502.
I think it will definitely make your life easier when it comes to scripts.
Enjoy it!
Note: Grammar errors are still hard to find since the code cannot run with a grammar error.
Comments