Lifetime of CALLBACK undocumented

Bug #1083193 reported by till
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
EPICS Application Developers' Guide
New
Undecided
Unassigned

Bug Description

From looking at the (3.14.12) code it is apparent that the CALLBACK argument to 'callbackRequest(CALLBACK *pcbck)' is passed by reference. However, it is undocumented for how long the CALLBACK object is in 'possession' of the callback facility, i.e., when it is safe to re-use a static CALLBACK object or to free a dynamically created one. In particular, it should IMO be documented/defined if it is safe to reuse or free a CALLBACK from the callback function itself. It does seem so under the current (3.14.12) code which does not access CALLBACK after executing the associated function but it would IMO be nice to document the exact semantics.

no longer affects: epics-base
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.