X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-type:content-transfer-encoding;
        bh=C2shB7YOAipAivmnkkIWobqayYydcCoZDh6rhGwYEoM=;
        b=frSmzH/B/r/ZGsfrzlmYJqimo0byB4w05jHJxaIjzABIuGi0mVuHRTCyDRhfW24p7n
         0EDwo6763Q2kiy74n8KtRoof+JCDznDqOYmlHt1h9mIFRJx+SuQd12ILOvjNjyqa65nG
         cSXTwoo33xMr/l1V6q2Zn9zAe3bwXuhBnswQyMMvTtgCayLiCOl7+5H+u97x8bGra9bw
         KSbwktNF2QolAFH33xALvVSb0vZc/MhdoGfmqGhqRi/3s/4TRiwjTFyX9tUWoyM5smqg
         RIhu368NPf2PEJoh14oelXhDLUhRG0RZuZGAzCxezkvp/ixxQgeBkUzx2ht4wPoWUP9h
         DNRw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-type:content-transfer-encoding;
        bh=C2shB7YOAipAivmnkkIWobqayYydcCoZDh6rhGwYEoM=;
        b=hbbM0I2D+4EuVNWXMiiMxQy5h758eRDR0zrxoFzv6gNQkyDhMwgpfSj22jWdgBLmUe
         QYagvqk7IJ/y2swbVkJCFAy6ZWdQiYrEGasJQsi5Io4jf7fzd9R1+4MPHm+gxxnLRUiw
         y4jJXjeqleDL3q/KiwEw/pwkJKEW2GBl8bSZMlb4S4Qgh42kTM8j5Dv1gkjhC6i25SDx
         oYf3P25pmlj7q+zcDLUvBY/0WnxVXjBnDBCv+x09Hki+A4Ho/aVVGozvNUD5JB5x2T+O
         Fy6CFauE314raEkmBNxeNE3fdaU+JKB8iUiaOSEPAspW2zzLOwhgcCtYsFJZsoQYdqtx
         3qpw==
X-Gm-Message-State: AG10YOQl5WIbysZxm+CFawovsAktyBDKJUQn5qRjOJK6lCjCkseJx8L2XwxzGkCbqzc6Cw==
X-Received: by 10.28.103.215 with SMTP id b206mr22803915wmc.93.1453770886084;
        Mon, 25 Jan 2016 17:14:46 -0800 (PST)
Date: Tue, 26 Jan 2016 02:14:40 +0100
From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Hierarchical design, pin number not needed
Message-Id: <20160126021440.f61e6e8be6bf4da5d2bafb25@gmail.com>
In-Reply-To: <8FA3D453-216B-489F-8862-EA004827B590@noqsi.com>
References: <20160125193136 DOT c1297d2b8e17f291e2250a4c AT gmail DOT com>
	<9763429C-BEFE-443F-B4E7-EDB3BA4FF55D AT noqsi DOT com>
	<20160125223859 DOT 8f1120bf6f98c3ca60ee2b00 AT gmail DOT com>
	<8FA3D453-216B-489F-8862-EA004827B590 AT noqsi DOT com>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> >>> Then using hierarchical design netlist complain if there are no pin numbers in symbol although in pcb it seems everything work OK without the pin numbers.
> >> 
> >> It doesn’t work OK if you’re not flattening hierarchy.
> > 
> > The number is in the symbol but not in the schematic underneath. How is the number used? Or what purpose does it fulfill?
> 
> There’s no way get get pin attributes or connections without the pin number in the back end. The hierarchy traversal in the core can “cheat” because it completely removes the pin from the netlist structures. A hierarchical back end needs the pin, though, and therefore needs the pin number.

So if hierarchical back end needs the pin how does it use it then there is only refdes and no pin number on sub sheet? Would it possible to add an enumerator in between instead?

Nicklas Karlsson