Subject: |
Re: [Merge] ~epics-core/epics-base/+git/Com:libcom-api into epics-base:7.0 |
From: |
Ralph Lange via Core-talk <[email protected]> |
To: |
mdavidsaver <[email protected]> |
Date: |
Mon, 25 Nov 2019 08:24:12 -0000 |
I like the cleaner approach!
As granularity is by library, every library will need a header file like libComAPI.h with functionally identical content. Instead of replicating the code - could this header be generated at compile time?
(I'm not so much concerned about the replication itself - more about the number of places that have to be patched if the mechanism ever needs to be changed.)
--
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.
- References:
- [Merge] ~epics-core/epics-base/+git/Com:libcom-api into epics-base:7.0 mdavidsaver via Core-talk
- Navigate by Date:
- Prev:
Re: [Merge] ~anj/epics-base/+git/base-7.0:typed-dsets into epics-base:7.0 Ralph Lange via Core-talk
- Next:
Build completed: epics-base base-7.0-363 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:
[Merge] ~epics-core/epics-base/+git/Com:libcom-api into epics-base:7.0 mdavidsaver via Core-talk
- Next:
Re: [Merge] ~epics-core/epics-base/+git/Com:libcom-api 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
|