Experimental Physics and
Industrial Control System

Andrew Johnson via Core-talk <[email protected]> · Fri, 03 May 2019 16:56:59 -0000

@Ben: Yes there are multiple scopes involved; redirecting stdin (e.g. "< envParams") or using the iocshCmd, iocshLoad or iocshRun commands all start a new scope. This was originally added for the iocshLoad and iocshRun commands which take a set of macro definitions, define them as environment variables for the duration of their script or command, and then pop the scope to undefine them afterwards. Here Michael is expanding the scope from just holding macro values to add his error handling state.

@Michael: Because it's not immediately obvious from the code, how do the different options behave from the perspective of someone writing a script, and especially one that gets called using iocshLoad? It looks like "on error break" exits the current script with an error, would that then trigger the "on error" mechanism in the calling script? Would we want an "on error abort [code]" to immediately quit the IOC? I'm not sure if that's necessary or not.

Is it possible for Keenan to hook into this mechanism from the synApps lua shell? I think that's important, would you he need you to add something like iocshGetError()?

In general I like this approach.

-- 
https://code.launchpad.net/~epics-core/epics-base/+git/Com/+merge/366876
Your team EPICS Core Developers is subscribed to branch epics-base:7.0.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System