Experimental Physics and
Industrial Control System

Thanks. The fact that db_post_events uses the original pointer as identifier explains the necessity to keep it intact. That was what I was missing.

I understand your second remark to refer to an API change, where we require the field index to be passed as a parameter to db_post_events instead of the pointer? I think everyone will agree that this is the "right thing" to do, but it would indeed be quite painful, since it affects all record types, not only those in base. The alternative you mention is not very convincing; if we shy away from the pain of an API change we can as well keep things as they are. But we really should add a comments in the code to explain this subtlety.
-- 
https://code.launchpad.net/~bfrk/epics-base/+git/epics-base/+merge/381308
Your team EPICS Core Developers is requested to review the proposed merge of ~bfrk/epics-base:zero-size-array-request into epics-base:7.0.

References:

[Merge] ~bfrk/epics-base:zero-size-array-request into epics-base:7.0 Ben Franksen via Core-talk

Navigate by Date:

Prev: Re: [Merge] ~bfrk/epics-base:zero-size-array-request into epics-base:7.0 mdavidsaver via Core-talk

Next: debugger w/ reverse execution Michael Davidsaver via Core-talk

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: [Merge] ~bfrk/epics-base:zero-size-array-request into epics-base:7.0 mdavidsaver via Core-talk

Next: Re: [Merge] ~bfrk/epics-base:zero-size-array-request into epics-base:7.0 Ben Franksen via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024