Experimental Physics and
Industrial Control System

Andrew Johnson <[email protected]> · Wed, 30 May 2012 10:29:11 -0500

Hi Michael,

On 2012-05-30 Michael Davidsaver wrote:
> 
> I just want to summarize my plans.  The branches I'm planning to propose
> for inclusion are the following.

Thanks...

> Ralph's server side plugins work.  The remaining work is to figure out
> how best to run the unit tests on RTEMS and vxWorks.
> 
> https://code.launchpad.net/~epics-core/epics-base/server-side-plugins

I added the necessary test harness files to the src/ioc/db/test directory on 
the 3.15 branch yesterday.  We will probably have to make some changes to the 
tests to ensure that they can all be run within the same process image though 
(you can only run iocInit once); I haven't looked at the tests so this might 
need some creativity...

> I pushed a few more revisions to
> 
> https://code.launchpad.net/~epics-core/epics-base/dontcant
> 
> these actually back out some of the changes already merged.  This
> re-adds some uses of cantProceed() to errors which are not allocation
> failures (epicsMutexMustLock() being one).

Re-merging that branch is not a problem.

> I'm also going to propose:
> 
> https://code.launchpad.net/~epics-core/epics-base/thread-pool
> 
> I think the API at this point is fixed.  I'm planning to replace the
> internal mutexs with something which can be used from interrupt context
> for RTEMS and vxWorks.

Vaguely related: I've just taken a look at jeff's epicsThreadOnce-atomics-
based branch which already has a merge proposal, but it has lots of text 
conflicts which will have to be resolved.

> And if I have time
> 
> https://code.launchpad.net/~epics-core/epics-base/callback-error
> 
> Although I think I will make some changes to this as well.  I'm having
> second thoughts about adding a field to the CALLBACK structure which
> existing code may not initialize correctly.

If the user's source code needs to be changed you should ensure that the 
compiler aborts with an error if they haven't made that change.  This is how 
we handled similar API changes between 3.13 and 3.14.

> Once I start the merge proposals I'll send another mail with links...

No need, each merge proposal notifies core-talk automatically.

- Andrew
-- 
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System