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=z3CVmDpcrC6XSOVU4MbLfybj5ZOTumhACjMgBIW00dE=;
        b=jbw/05trIBtlwHOfx8D81OFSbcIGyroRdMMGzT9f2YBlNiN1DYkYDFcQhD6dTkzvpY
         WnRTmXxfZJz1sc7Wo2302uttBUBnQ+b8LhSiNfB06vIR4LEEg2/78kTYRhLphZ9+ANR0
         wSd1NIbDv6YHN8J/5qEgMFlLCcQwvEkUCHY+G/sGxa5488cZX2j5ay5Z3rUaV8beywS8
         e8pxkjOOepK2+ztEkGYRqbzivryFRcUrR7ZgnGewCuA70Q99V9AfKgrq8Dep++lLzm7a
         XBD7OAOyPpgbQr6o+182JPyuCiCaTbzDxBahN+yA28tRnZtuzQNk0nUwdQ2iuqCyrS71
         m0HA==
X-Received: by 10.112.157.69 with SMTP id wk5mr28408906lbb.74.1451763110968;
        Sat, 02 Jan 2016 11:31:50 -0800 (PST)
Date: Sat, 2 Jan 2016 20:31:49 +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] ideas on slotting and mechanisms for
 grouping/associating heterogenous symbols.
Message-Id: <20160102203149.375887378ec1a58ee7e9bc79@gmail.com>
In-Reply-To: <201601021843.u02IhC5U021940@envy.delorie.com>
References: <CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com>
	<8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1512300544550 DOT 9035 AT igor2priv>
	<87FC7D4C-157A-499E-8B93-97653D6A7C68 AT noqsi DOT com>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1601012231450 DOT 1728 AT newt>
	<AE52C1DB-01A3-43FA-AE8E-68AD33F37180 AT noqsi DOT com>
	<624E6A69-62CE-4FCB-9D44-9FDF036254A3 AT sbcglobal DOT net>
	<56880043 DOT 7040003 AT ecosensory DOT com>
	<20160102182739 DOT 5d195829880cf75768ae0a82 AT gmail DOT com>
	<201601021755 DOT u02HtOWs020325 AT envy DOT delorie DOT com>
	<20160102191018 DOT 5e68c0c4ecc70a49bd9998f6 AT gmail DOT com>
	<201601021816 DOT u02IGHCC021127 AT envy DOT delorie DOT com>
	<568817CC DOT 7090207 AT ecosensory DOT com>
	<201601021843 DOT u02IhC5U021940 AT envy DOT delorie 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=US-ASCII
Content-Transfer-Encoding: 7bit
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

> Your example isn't the example I was thinking of.  Consider this schematic:
> 
> http://www.delorie.com/pcb/symsym.png
> 
> In layout, you swap one of those gates with a gate in U2 (elsewhere).
> 
> How do you know which gate you swapped?
> 
> There's nothing in the schematic to make those two gates unique, other
> than where they fit in the geometry of the page.

Schematic is the same regardless of which gate is used so there really is no need to know where i ended up, problem is similar as in software then there usually are no need to know at which address a variable is stored.

If swapping between refdes is allowed back annotation is needed and in such case I guess refdes could be left empty and assigned automatically just as nets without a name.

For actual choice made later during design flow it could done with back annotation which may be a little bit complicated or forward annotate for documentation purpose.


Nicklas Karlsson