On Fri, 2019-02-22 at 14:15 +0100, Juergen Schoenwaelder wrote: > On Fri, Feb 22, 2019 at 12:45:16PM +0000, Balázs Lengyel wrote: > > I am not asking for a change, but ... > > > > IMHO it would be better if YANG would not allow whitespace in enum names. > > It is a rarely needed freedom that degrades usability and can lead to > > mistakes > > and higher tool development costs. So it is bad for both people and > > tools. > > > > * It is misleading, as a human user can mistakenly think that "this is > > legal" is actually 3 separate values > > * Some tools tend to consider spaces as separators > > * When creating code from YANG this needs special handling > > > > Banning white space may make you feel better but it does not really > solve the problem for tool makers. There are many more restrictions > and going for the most restricted minimum gets us back to really > limiting results.
I agree. It is not terribly difficult to support enum names containing spaces in any programming language. Lada > > /js > -- Ladislav Lhotka Head, CZ.NIC Labs PGP Key ID: 0xB8F92B08A9F76C67 _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
