I'm also in agreement with Dirk, though I won't go as far as Ben. "a
few records" doesn't capture the potential effects. At the time, these
are 'potential' effects. Based on lackluster response to my tech-talk
mail, I think the reasonable course of action is to add new restrictions
as warnings. These would remain warnings for some years to give sites
an opportunity to notice them and request changes. I would then lean
towards loosening restrictions to avoid orphaning whole sites from
future updates.
So I begin with:
https://github.com/epics-base/epics-base/pull/78
--
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1882520
Title:
Constant arrary input links of size 1 don't work
Status in EPICS Base:
In Progress
Bug description:
Constant input links in array form with 1 element don't work and
return an empty array.
Example:
field (INP, [42])
As soon as a comma is present, it works:
field (INP, [42,])
To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1882520/+subscriptions
- References:
- [Bug 1882520] [NEW] Constant arrary input links of size 1 don't work Dirk Zimoch via Core-talk
- Navigate by Date:
- Prev:
Build failed: epics-base base-alarm-msg-544 AppVeyor via Core-talk
- Next:
Build failed: EPICS Base 7 base-7.0-28 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:
[Bug 1882520] Re: Constant arrary input links of size 1 don't work Andrew Johnson via Core-talk
- Next:
[Merge] ~dirk.zimoch/epics-base:fix_one_element_input_link_arrays into epics-base:7.0 Dirk Zimoch 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
|