Default DISP to TRUE for all In records #74
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will default the
DISP
field toTRUE
for all In record types.PythonSoftIOC In records never perform processing, and so are never given an opportunity to access the .VAL field, even if a
caput
has updated it. This means that while acaget
call would return the new value, arecord.get()
call would not which would lead to confusion.By setting DISP=TRUE we disable
caput
from changing the value and thus maintaining consistency betweencaget
andrecord.get()
values.Note that it is possible to use
caput
to change the DISP field, but if users do this it's on them. I'm not sure there's any way to stop them doing this if they really want to.This could be a breaking change, depending how well behaved people have been with In records. @MJGaughran gave the example of an In record being used as an input to a CALC record. And of course the more general use-case of someone just doing
caput
to an In record, when they probably should have been using an Out record.