get_alarm_double() inconsistent across record types
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
EPICS Base | Status tracked in 7.0 | |||||
3.14 |
Fix Released
|
Low
|
Ralph Lange | |||
3.15 |
Fix Released
|
Low
|
Ralph Lange | |||
3.16 |
Fix Released
|
Low
|
Unassigned | |||
7.0 |
Fix Released
|
Low
|
Unassigned |
Bug Description
The get_alarm_double() method of the Record Support API is implemented inconsistently across record types.
E.g.
The longin record uses
if(
} else recGblGetAlarmD
If the channel is the VAL field, the elements are set from the four fields of the record, NaN otherwise.
The ai record uses
if (dbGetFieldInde
} else recGblGetAlarmD
If the channel is the VAL field, the elements are filled from the four fields if the appropriate severity is set.
The inconsistency was introduced in 3.14.11 by commit c0052ea (https:/ /git.launchpad. net/epics- base/commit/ ?h=3.14& id=c0052ea44f3b efdb99089228a1e 57956338a478b) that was changing only the records with double type values.