Having statements default/mandatory in the model that seem to mean
something, but practically have no effect is most confusing.
Balazsd
On 2015-10-06 11:24, Balazs Lengyel wrote:
Hello,
Some more corner cases for embedded choices, with my solutions in
them. How an average operator or even model implementer would figure
these out is anyone's guess. regards Balazs
choice scen9 {
case A {
choice subChoiceA {
mandatory true; // this mandatory has
absolutely no effect as the case A above might not exist
case A {
leaf scen12-num1 { type uint8; default 1;
} // this default has absolutely no effect
// if the leaf exists it has a
value if you delete it the whole choice scen9 becomes empty
}
case B {
leaf scen12-num2 { type uint8; }
}
}
}
case B {
leaf scen12-num1 { type uint8; }
}
}
--
Balazs Lengyel Ericsson Hungary Ltd.
Senior Specialist
ECN: 831 7320
Mobile: +36-70-330-7909 email: [email protected]
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
