Hi,
Is there any practical value of 'when' statements with circular
dependency to the value of the parent (in case it is a leaf) or any
children of the parent?
container circular-dependency-when {
leaf a {
when "(. + ../b) = 100";
type uint16 {
range "0 .. 100";
}
}
leaf b {
type uint16 {
range "0 .. 100";
}
}
}
I notice none of the tools known to me complain about this example
model however some will not allow the user to interactively configure
'a' (even if he intends to use value which would make the 'when'
statement evaluate as "true").
Did not find any 'when' statements depending on the value of their
parent or the value of children of that parent in the standard and draft
models known to me but this is valid YANG according to the YANG RFC text.
I believe if there is consensus this indeed qualifies as circular
dependency and it has no value to allow such cases it can at least give
a signal to model designers they should avoid using such 'when'
statements until this is explicitly noted in a follow up YANG version.
Vladimir
_______________________________________________
netmod mailing list
netmod@ietf.org
https://www.ietf.org/mailman/listinfo/netmod
