Re: [YANG] import statement

Ladislav Lhotka <lhotka@cesnet.cz> Sat, 03 May 2008 14:00 UTC

Return-Path: <yang-bounces@ietf.org>
X-Original-To: yang-archive@optimus.ietf.org
Delivered-To: ietfarch-yang-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A716A3A6CCC; Sat, 3 May 2008 07:00:37 -0700 (PDT)
X-Original-To: yang@core3.amsl.com
Delivered-To: yang@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BD133A6CCC for <yang@core3.amsl.com>; Sat, 3 May 2008 07:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.399
X-Spam-Level:
X-Spam-Status: No, score=-0.399 tagged_above=-999 required=5 tests=[AWL=-0.638, BAYES_05=-1.11, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UpmBSD5wan+2 for <yang@core3.amsl.com>; Sat, 3 May 2008 07:00:36 -0700 (PDT)
Received: from office2.cesnet.cz (office2.cesnet.cz [195.113.144.244]) by core3.amsl.com (Postfix) with ESMTP id 4878A3A6B0B for <yang@ietf.org>; Sat, 3 May 2008 07:00:36 -0700 (PDT)
Received: from [172.29.2.201] (asus-gx.lhotka.cesnet.cz [195.113.161.161]) by office2.cesnet.cz (Postfix) with ESMTP id 7795AD800C0 for <yang@ietf.org>; Sat, 3 May 2008 16:00:37 +0200 (CEST)
From: Ladislav Lhotka <lhotka@cesnet.cz>
To: yang@ietf.org
In-Reply-To: <20080503120217.GA24899@elstar.local>
References: <1209812833.14759.12.camel@missotis> <20080503120217.GA24899@elstar.local>
Organization: CESNET
Date: Sat, 03 May 2008 16:00:37 +0200
Message-Id: <1209823237.14759.24.camel@missotis>
Mime-Version: 1.0
X-Mailer: Evolution 2.12.1
Subject: Re: [YANG] import statement
X-BeenThere: yang@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: YANG modeling Language for NETCONF <yang.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/yang>
List-Post: <mailto:yang@ietf.org>
List-Help: <mailto:yang-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yang>, <mailto:yang-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Sender: yang-bounces@ietf.org
Errors-To: yang-bounces@ietf.org

Juergen Schoenwaelder píše v So 03. 05. 2008 v 14:02 +0200:
> > 
> > module foo {
> >   namespace "urn:foo";
> >   prefix foo;
> >   container foo-cont {
> >     leaf foo-leaf {
> >       ...
> >     }
> >   }
> > }
> > 
> > module bar {
> >   namespace "urn:bar";
> >   prefix bar;
> >   import foo {
> >     prefix foo;
> >   }
> >   container bar-cont {
> >     leaf bar-leaf {
> >       ...
> >     }
> >   }
> > }  
> 
> No. An import simply means that the names defined in the imported
> module become known and accessible - there are no side-effects of
> imports.

Then the one and only way for utilizing the imported name "foo-cont" in
module bar is in 

  augment /foo:foo-cont {
    ...
  }

which results in placing (possibly augmented) copy of the "foo-cont"
container at the location of the augment statement. Or am I missing
something?

Lada

-- 
Ladislav Lhotka, CESNET
PGP Key ID: E74E8C0C

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