| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [Merge] ~dirk.zimoch/epics-base:FilterForInfoFields into epics-base:7.0 |
| From: | mdavidsaver via Core-talk <core-talk at aps.anl.gov> |
| To: | mp+399414 at code.launchpad.net |
| Date: | Wed, 10 Mar 2021 16:40:25 -0000 |
As I see it, there previously were three states for a db_field_log to be in: 1. Simple value type==dbfl_type_val 2. Owned value type==dbfl_type_ref 3. Borrowed value type==dbfl_type_rec I think these would now need to be represented as: 1. type==dbfl_type_val && !dtor 2. type==dbfl_type_ref && dtor 3. type==dbfl_type_ref && dtor Where 2 and 3 are ambiguous, and handling #2 would unnecessarily require dbScanLock() Do I have this correct? -- 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.