| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [Merge] ~epics-core/epics-base/+git/Com:libcom-api into epics-base:7.0 |
| From: | Ralph Lange via Core-talk <core-talk at aps.anl.gov> |
| To: | mdavidsaver <mdavidsaver at gmail.com> |
| Date: | Sun, 01 Mar 2020 11:30:49 -0000 |
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.