Re: [Merge] ~epics-core/epics-base/+git/Com:iocsherr into epics-base:7.0

[mdavidsaver via Core-talk <core-talk@aps.anl.gov>]

> Why?

I'm regretting the exposure of iocshCmdDef::func and allowing outside code to directly call iocsh functions.  In retrospect, we should have insisted on having a wrapper function such as is being discussed now.

> handle "on" being called without the ioc shell being started, but you don't actually have to handle any of that

True, this is either "defensive programming", or laziness.  Easier to test for NULL than decide if it is impossible.  This is in part to ensure that external code (yours being the only I know of) won't be broken.

Maybe the question is whether you are motivated to work on this yourself?

And I suppose we are all dancing around the question of if/when to rewrite iocsh.cpp (as actual c++), or replace it with (something like) a lua interpreter shell.
-- 
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.