Hi Lewis,
Good question. In general the answer is any API that isn’t in the 3.15.x release series may need updates after we’ve made use of it for a while. Specifically though:
1. The extensible link support and JSON Link APIs (dbJLink.h and dbLink.h) may change to some extent, hopefully not by much but until we have fully implemented CA, DB and PVA links in the new JSON style we won’t know for sure.
2. The current JSON parser doesn’t handle 64-bit integer literals, but the above APIs were modified to allow that fix to be added without changing the method signatures. I don’t know if we modified the channel filter API though.
As always we can’t be sure about the future need for changes, but the above were the main items I was thinking about when I wrote the note below. If I’ve missed anything Michael Davidsaver may have some additional notes.
HTH,
- Andrew
> On Jun 5, 2017, at 9:41 AM, J. Lewis Muir <[email protected]> wrote:
>
> On 06/02, Andrew Johnson wrote:
>> Note that some of the new APIs included with this release are not
>> considered "final" and may change in the future. Please tell the core
>> developers if you plan to develop software using these APIs.
>
> Hi, Andrew.
>
> How do I know which APIs are not considered final?
>
> Thanks!
>
> Lewis
- References:
- EPICS Base-3.16.1 Released Andrew Johnson
- Re: EPICS Base-3.16.1 Released J. Lewis Muir
- Navigate by Date:
- Prev:
Re: EPICS Base-3.16.1 Released J. Lewis Muir
- Next:
EDM X-Y Graph lot widget oddities Eric Norum
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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: EPICS Base-3.16.1 Released J. Lewis Muir
- Next:
Use default value if CA link error Luca Cavalli
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|