Would that be a limitation applying to libCom scope only, or more general.
As a general limitation, I have a gut feeling that this will backfire / break existing user code.
We would at least have to provide a migration guide showing how to deal with situations where multiple libraries are created in one place.
--
https://code.launchpad.net/~epics-core/epics-base/+git/Com/+merge/375942
Your team EPICS Core Developers is requested to review the proposed merge of ~epics-core/epics-base/+git/Com:libcom-api into epics-base:7.0.
- Navigate by Date:
- Prev:
Build failed: epics-base base-7.0-8 AppVeyor via Core-talk
- Next:
Build failed: epics-base base-epicsTempFile-C-9 AppVeyor 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] ~epics-core/epics-base/+git/Com:libcom-api into epics-base:7.0 mdavidsaver via Core-talk
- Next:
Re: [Merge] ~info-martin-konrad/epics-base:fix-crash-dbloadrecords-after-iocinit into epics-base:3.15 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
|