** Also affects: epics-appdev
Importance: Undecided
Status: New
** No longer affects: epics-base
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Application Developers'
Guide.
https://bugs.launchpad.net/bugs/1083193
Title:
Lifetime of CALLBACK undocumented
Status in EPICS Application Developers' Guide:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-appdev/+bug/1083193/+subscriptions
- Navigate by Date:
- Prev:
Re: RFC: libCom/osi - new spinlock API Andrew Johnson
- Next:
RE: Base R3.14.12.3-pre1 available nick.rees
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Base R3.14.12.3-pre1 available nick.rees
- Next:
mbboDirect changes Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|