Experimental Physics and
Industrial Control System

mdavidsaver via Core-talk <[email protected]> · Fri, 06 Sep 2019 17:49:49 -0000

> Is your plan to mark CALLBACK with EPICS_DEPRECATED at some point?

As a matter of form, yes.  Though there is no urgency.

> applied to 3.15

Not "of course" for me, but your decision.  As you've indicated approval, I'll apply to 3.15 directly w/o another MR.

> If you were to move

I'll work on cures, but I'm tired of treating this symptom.  Someone else will need to find an appropriate bandage this time.

I could pick 299aed026fd40b792f40b08386f208d17166fc40 onto 3.15 as well,
which also fixes things going forward.

> need Release Notes

Yup.  I going to wait until any formatting changes have landed.  The entry will be:

Add option to avoid CALLBACK conflict.

If a macro EPICS_NO_CALLBACK is defined, then callback.h will no longer (re)define CALLBACK.
The name 'CALLBACK' is used by the WIN32 API, and redefinition in callback.h cause errors if some windows headers are later included.

Code which defines EPICS_NO_CALLBACK, but still wishes to use callbacks, should use
the alternate name 'epicsCallback' introduced in 3.15.6, 3.16.2, and 7.0.2.
It is also possible, though not encouraged, to use 'struct callbackPvt'
which has been present since the callback API was introduced.
-- 
https://code.launchpad.net/~epics-core/epics-base/+git/database/+merge/372385
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