X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 207.224.51.38
X-Authenticated-UID: jpd AT noqsi DOT com
Content-Type: multipart/signed; boundary="Apple-Mail=_FABC8C7D-1ACC-4D72-9CD5-873293ACC47D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [geda-user] Pin mapping (separate symbols from mappings)
X-Pgp-Agent: GPGMail 2.5.2
From: John Doty <jpd AT noqsi DOT com>
In-Reply-To: <201510191858.t9JIwMIB029296@envy.delorie.com>
Date: Mon, 19 Oct 2015 13:30:21 -0600
Message-Id: <8EAEFD56-9005-4AF8-B298-77983D29B4C0@noqsi.com>
References: <20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com> <201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com> <20151018234424 DOT c0551dad9bef0859130239d9 AT gmail DOT com> <36B94694-F2AC-4A75-A8EB-40A1CE9A534C AT noqsi DOT com> <201510182225 DOT t9IMPkxK032763 AT envy DOT delorie DOT com> <20151019003814 DOT f62620bf0fec77e65104c105 AT gmail DOT com> <BED51F9A-F6FF-4A23-B18B-C2EC8BB9DAB6 AT noqsi DOT com> <201510190242 DOT t9J2gl7w009345 AT envy DOT delorie DOT com> <282EF9EF-E103-4101-BB56-A0A365AFFEBE AT noqsi DOT com> <201510190408 DOT t9J48ZbC015157 AT envy DOT delorie DOT com> <F9B802B2-A8F6-4A6F-9429-02161A60B6C5 AT noqsi DOT com> <201510190502 DOT t9J528LM019325 AT envy DOT delorie DOT com> <58E58C85-9493-47DD-AC5B-AD78C33A712A AT noqsi DOT com> <201510191640 DOT t9JGeWb0024375 AT envy DOT delorie DOT com> <4AC7F055-0A26-4DD8-B8F9-8D67F7E36B0A AT noqsi DOT com> <201510191722 DOT t9JHMi7G025782 AT envy DOT delorie DOT com> <EE86E5DE-3251-4B76-B3A1-7FE471FCB539 AT noqsi DOT com> <201510191858 DOT t9JIwMIB029296 AT envy DOT delorie DOT com>
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.1878.6)
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


--Apple-Mail=_FABC8C7D-1ACC-4D72-9CD5-873293ACC47D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 19, 2015, at 12:58 PM, DJ Delorie <dj AT delorie DOT com> wrote:

>=20
>> Well, I think that's a logical requirement, not a mere desire.
>=20
> I'm glad you agree with yourself.  We're back to my original
> supposition, that *if* it's required, *one* of the options is a UUID.
>=20
>>> No, (3) only requires a UUID be assigned to each symbol as it's =
instantiated.
>>=20
>> Until you realize that users make copies of things using multiple
>> methods, and the intent of the copy may be to move the circuitry or
>> to duplicate it. Then, it still requires clairvoyance.
>=20
> We've discussed this in the past, and generally agree that "path to
> object in design" needs to be part of the uniqueness, in order to
> differentiate between one symbol showing up in multiple places in a
> heirarchy.  This plus "unique on page" (as long as the key to
> uniqueness doesn't change over time) is probably sufficient to
> uniquely correlate an instance in <downstream> to one symbol in the
> project.

You forget that one way to make a variant page is =93cp page1.sch =
page2.sch; gschem page2.sch=94. Gschem can=92t know that you=92ve done =
this, but it is a useful technique when you have repetition with =
variation. Another interesting case is where you copy/paste to a =
different page. These are only the cases I can think of right now.

Once you=92re enumerating use cases, trying to come up with a solution =
to each one, you=92re not thinking flexibility anymore.

> But we also generally agreed that a heirarchical schematic
> would need to be flattened to produce an as-built anyway, which limits
> that problem somewhat.
>=20

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com



--Apple-Mail=_FABC8C7D-1ACC-4D72-9CD5-873293ACC47D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJWJUTNAAoJEF1Aj/0UKykR7+UP/jq9CygfMJIFiFdyzoKAifsR
nwiT5Y7fs27sXnHtT5rH84oLlRAvUwaRw+okwRJY85gNQq+7xd3gZaVXE7BhgsJ6
AjKa0VajvwlGsqDQmk2VCckSdfhtOCcc5hYSoRXV9jXcDxjqLdsRRu6xulaOwRRZ
kRGlLCA/rRpyXeC5B6V9RRz2JKqXQbm8BvhVhQsPfmb/0/jnNuqZu6sYoE1zpJ2u
N/bAtpGjGikEaL0haJvNUmbAlhz3MEfpaRXOdjG6n8wvRMJOGuyP9zla+LdkPiVQ
z55piryZilOi6kOXOsFskzil+Rfv4+QXf5lVq7Ql6bzlUBtxGJrS6CGYaog9k0wK
l1EFHvdcqnJspFCS7wvLo/UAZGJw/dyGz5pGlztyyRCPhj9tvUjkxKOER5miX0/I
Kug7VfIN9tRN5jrtiz1VwBaIJJTgM9RvCDN72GRp6+esEdHJFvEEAMu0/iM4WrGe
lo4BeIajXJPIYLUIPqKZvDI3DeibL5X1RTplotEic4LaP56xxSaEhf8ZTgO34J/c
Z6DXqj0bOqeVMWCkaK7V+6Eo8eMfiSLu1YHswW7jXrc62uzGVcprMdYQfgfZZ03T
MrATldjEMLUoJoakErgIvm5WlXHr6YoozIMqnLwHi1hNf+sLYuxA0gFz9hWQFNyK
WBB5R8sNTBRfH3eBRbtp
=8e2q
-----END PGP SIGNATURE-----

--Apple-Mail=_FABC8C7D-1ACC-4D72-9CD5-873293ACC47D--