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=Cgsa6ZuqRW1lwZDmZjzkRqps9S8AX226NrDTsA2Tq8s=;
        b=J5qilfUkhA9C9F3L/8PsCftJNFbHEzMBJrSvlpVAsv0u1HDkr3tMXSYX34nk/K56Hc
         2HGdTgNX94JmzHpiL8Zz5iXOj6ECBiVGHMK3MbIq4qKLswFBuKu6OcYjBpd8oV0QNMKf
         27N6n3JRziIz482gb3RTHnTkevOn8xdDIFm3irCeJsR6IXTXkzyOPo8JNPF/t9pz86V1
         05P1NnXcXqZ7R+azHsnn+MHrq0u+uh2ah/qjxaTRYm2EZ/j1DosbVhsOkWDTR3/8pEP9
         olDP+7ocJuLl/Rz7PHhpxUC+dZnpMSPMFfweO0yJXmhf3oxJ+Ffk1XnqRw2fjdtNx8dx
         5KWA==
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=Cgsa6ZuqRW1lwZDmZjzkRqps9S8AX226NrDTsA2Tq8s=;
        b=MU8i59lrv1dZUqj42ZASPL7jFhpD4hQohK+jQfEuxet+wv0prEk2CEYASQWQeg5Hsu
         chwesmGCgvB5AXZXQT2HDoj2p/vWubOUt/y9vl3EAkEcX9PoqYdtGoaNToJMHiNmnmuS
         huA6M54me8nCGlY0/WaBve45QQKReTJ08CMJ6UapYpnHZX/lng/hWdbDrTXHNGyjWaGR
         eUB9fY9B9LXkNl2NG4J5PerX+WSFMsNJ+ytkslDrD2TqGaAk+wTfZr91Tg8pnojqi7JB
         5O+jzVRhSZFpKvJV0zfYTANH5kx9DLkhUpG7ekUgtZHLSXauA5UGi5mtcP3wGA1QTMV1
         ZgTA==
X-Gm-Message-State: AG10YOSBnvRrxmv1Pv9dc6Ez4c6X2i2N5HvTvdNahRIN8yaBcw4gmA0b+P4VlyFErk9D9w==
X-Received: by 10.28.174.196 with SMTP id x187mr23944489wme.2.1453799047687;
        Tue, 26 Jan 2016 01:04:07 -0800 (PST)
Date: Tue, 26 Jan 2016 10:04:02 +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: <20160126100402.55b76b26cdc848856d4f7ad5@gmail.com>
In-Reply-To: <8DF71CDE-4E0D-481B-B240-99FAFE082328@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>
	<20160126021440 DOT f61e6e8be6bf4da5d2bafb25 AT gmail DOT com>
	<8DF71CDE-4E0D-481B-B240-99FAFE082328 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?
> 
> It depends on the back end. The older SPICE back ends relate the numeric part of a spice-IO device’s refdes to a pinseq attribute on the subcircuit symbol. My gnet-spice-noqsi imitates the gnetlist core behavior, relating the refdes on an io symbol to the a pinlabel on the subcircuit symbol. I don’t know what other hierarchy-aware back ends do.

Since gnetlist and your gnet-spice-noqsi relate the refdes on an io symbol to the pinlabel there should be no need for pinnumber then using these backends since the number is not used.


Nicklas Karlsson