Re: [YANG] Questions about submodule

Hi Yan,

Li Yan <liyan_77@huawei.com> wrote:
> Hi,
> 
> o Sec 7.2.1 tells me that the "submodule" statement can contain the
> "include" statement.
> 
> Does it imply that a submodule can be split further into multiple
> submodules, and the separation is recursive?

Yes.  One use case for letting a submodule include another one is when
you split a larger module into submodules, and you want a submodule
with common types:

   main-module:  includes sub-a, sub-b, sub-common-types
   sub-a: includes sub-common-types
   sub-b: includes sub-common-types

> I think splitting submodule would complicate the relationship between
> submodules, and is not useful.

In larger projects, this might actually be useful.  Instead of having
one big centralized module, we allow people to split the task into
submodules.  If the submodule becomes big enough, it might be useful
to split it into other submodules.  Even though I cannot see that 100
levels are ever used, I don't think we should add a rule which says
that you cannot nest more than 99 levels.

> o A typo question
> 
> The following examples are from sec 7.1.10 and 7.2.3 respectively. I am
> confused if the module/submodule name should be quoted.
> 
> module acme-system {
> 
>     .
> 
>     include acme-types;  //no quotes
> 
>     .
> 
> }
> 
> submodule acme-types {
> 
>     belongs-to "acme-system";  //in quotes
> 
> .
> 
> }

The argument to a statement is always a string.  Quotes MUST be used
if the string contains whitespaces etc, ane MAY be used otherwise (see
6.1.2 and 6.1.3).  So the examples above are both correct.

/martin

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang