OMSL="closed_loop" doesn't work with constant DOL
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
EPICS Base | Status tracked in 7.0 | |||||
3.15 |
Fix Released
|
Low
|
Andrew Johnson | |||
7.0 |
Fix Released
|
Low
|
Andrew Johnson |
Bug Description
This was incorrectly documented for the boRecord. I just fixed that in the wiki.
However, I see this as yet another arbitrary limitation.
To lift that we need a small generalisation to how we treat constant links. A constant link just has to remember whether it has been processed before. The flag gets set by dbGetLink and the like and it gets reset after link initialisation (so we can change the "constant" using a CA put to the link field). If dbGetLink finds that the link is constant, then it converts the value from the string stored in the link, but only if it hasn't been processed before. This also means that we can deprecate recGblInitConst
summary: |
- OMSL doesn't work with constant DOL + OMSL="closed_loop" doesn't work with constant DOL |
FWIW:
Record descriptions have been converted to POD and moved into the .dbd.pod files at the recent documentathon. Those changes have been added as merge proposals, some of which might still be pending their merge.