Re: [yang-doctors] guideline for enum and value?

["Acee Lindem (acee)" <[e-mail]>]

I agree. 

On 2/14/18, 11:00 AM, "yang-doctors on behalf of Juergen Schoenwaelder" <[e-mail] on behalf of [e-mail]> wrote:

    On Wed, Feb 14, 2018 at 04:47:40PM +0100, Juergen Schoenwaelder wrote:
      
    > > And:
    > > 
    > >  Do not use explicit 'value' statements, except if:
    > >     o the enum corresponds to some standard integer value, or
    > >     o you update the set of enums by inserting new enums in the middle of
    > > the list
    > 
    > I am not sure why we would recommend this.
    >
    
    More specifically, I do not see why
    
      type enumeration { enum foo { value 0; }; enum bar { value 1; }; }
    
    is to be avoided in favor of
    
      type enumeration { enum foo; enum bar; }
    
    given that they mean the same and the first one is explicit and robust
    to changes while the second one must be handled with care (only append
    enums, never reorder enums). Yes, clueful YANG authors can handle the
    later fine as they will understand that if order changes are needed,
    you have to move to explicit value assignments. My fear is that not
    all YANG authors will be aware of this (but then many of those authors
    likely also do not read guidelines).
    
    /js
    
    -- 
    Juergen Schoenwaelder           Jacobs University Bremen gGmbH
    Phone: [phone]         Campus Ring 1 | 28759 Bremen | Germany
    Fax:   [phone]         <https://www.jacobs-university.de/>
    
    _______________________________________________
    yang-doctors mailing list
    [e-mail]
    https://www.ietf.org/mailman/listinfo/yang-doctors