Experimental Physics and
Industrial Control System

> 1. Ignore the previous value
> 2. dtor it
> 3. copy new pointer and install new dtor.
> 
> That means those two line in question implement item 2 and need to stay.

I see. So this guards against a configuration error: someone applies the info item filter on top of some other filter. Such a configuration doesn't make sense, but we have to do something and I guess your solution is acceptable.

I would want to get a warning in this case, but certainly not every time the filter gets processed, rather only once when the filter is set up. Do you think that could be done?
-- 
https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+merge/399414
Your team EPICS Core Developers is requested to review the proposed merge of ~dirk.zimoch/epics-base:FilterForInfoFields into epics-base:7.0.

References:

Re: [Merge] ~dirk.zimoch/epics-base:FilterForInfoFields into epics-base:7.0 Dirk Zimoch via Core-talk

Navigate by Date:

Prev: Re: [Merge] ~dirk.zimoch/epics-base:FilterForInfoFields into epics-base:7.0 Dirk Zimoch via Core-talk

Next: [Bug 1918614] [NEW] epicsLoadTest fails when INSTALL_LOCATION is set Dirk Zimoch 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] ~dirk.zimoch/epics-base:FilterForInfoFields into epics-base:7.0 Dirk Zimoch via Core-talk

Next: Re: [Merge] ~dirk.zimoch/epics-base:FilterForInfoFields into epics-base:7.0 mdavidsaver 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