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=sbcglobal.net; s=s2048; t=1451690374; bh=xLr19kX2BxJNK1Tkpm8jEFBY18uN/y4RP+rYaQHUqdc=; h=Subject:From:In-Reply-To:Date:References:To:From:Subject; b=fEqiAgGIjPKfsvd1K6tWKBTxGVLshFV+rxqFNfoj6dWF+xhxRGL2bbdiNDDzLB8rqyOJtk+hqBL2z74h8kUzt3t1aA0r6iavrjx8LUnaMsq7cbSinudbB+U5BYhHXpBerG59StQRG/t3xgGf00Sbj+vE+GZUTiN+UBqvu/yHeYF0hc/Ktk9aitrnnV5AJMZJTjy9vse5Wt/ME+G6Jjo+zJHgz3QSrP9MZFwNjzfLDIcyrMDfM8bv9oDzCnkdYvzWFkAGclV/YdvZqamh2Hzt6mMtf5+kwk1EsWQNqt9MONtrG8vc8Yxhs6903aUDEpWfhKY6zJDffQi3J0iidQjzag==
X-Yahoo-Newman-Id:	144399 DOT 48990 DOT bm AT smtp224 DOT mail DOT gq1 DOT yahoo DOT com
X-Yahoo-Newman-Property:	ymail-3
X-YMail-OSG:	aEUjT5cVM1nnyb4G7J5G7YFa8MDjDtZkQamM98hJ1eEdA4G
	apjqxulJ82icSt1NL6Pa8Krf7NaO_DeYKNXmaJL8gHOM3WwtVYxz6FzhE_32
	s5v2Q9nliUl92qfzg_wzaGbV26pjPhAl61ewBRwtJz6IRtqx8F2p.lMYSYpS
	VAGOZJk4RtP6T.Xo3Xi9Jv0u0l_KekREnm.V3MYECkFe0N3op7u5.Ip561uf
	mdYLX6zyuv10TRAdE3VMNVWVPPV281nKcrO8ELtn2BcRShiDjY1hIEZNsx66
	wOVLQD_tvvM_1Hj5CCNT1tbgRQMCLxFMWAuwtGmQrr4QsvRR3SDtX_YW7hKO
	zJvbpoPIBhAAEUGQuXfe2cPin13_GzJARJBg7WY_IBK9akDkiZv0ax.i8g7I
	22pUOlTb24NwJpyYAXnXtjslNF_32OYyuPSEcZZ65JGjnl8y9NKFrbf6a4EV
	RX8moiWV_cpaBy0GAKtQusTUwT5kTnc6kaeHjf_CsKV7xQj0d9q6R5JKQIvR
	AgQNjCtEIlRN44yW09UoRSQqgagefx6c.mrxtQk.t470pVpOGTg--
X-Yahoo-SMTP:	b8jVkbOswBAqZ4BhECp7nxPJUfTGEnEGv_G4qgQeZMeAbA--
Mime-Version:	1.0 (Mac OS X Mail 8.2 \(2104\))
Subject:	Re: gEDA and it's future with Scheme & Guile was Re: [geda-user] Project leadership
From:	"Edward Hennessy (ehennes AT sbcglobal DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
In-Reply-To:	<AE52C1DB-01A3-43FA-AE8E-68AD33F37180@noqsi.com>
Date:	Fri, 1 Jan 2016 15:19:32 -0800
Message-Id:	<624E6A69-62CE-4FCB-9D44-9FDF036254A3@sbcglobal.net>
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>
To:	"geda-user AT delorie DOT com" <geda-user AT delorie DOT com>
X-Mailer:	Apple Mail (2.2104)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id u01NJbqe018986
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

> On Jan 1, 2016, at 2:53 PM, John Doty <jpd AT noqsi DOT com> wrote:
> 
> Various people have suggested various approaches over the years. I would invite them to restate their positions or point us at their posts.
> 
> One problem with heterogeneous slotting is knowing when a bunch of symbols with the same refdes form a complete description of a part without duplication. My gnetlist back ends gnet-check-pincount and gnet-check-duplicates are effective at detecting errors in heterogeneous slotting from the bottom up. They don’t require that the symbols somehow encode the knowledge of which other symbols they should partner with.

I would be interested to hear everyone’s ideas on slotting and mechanisms for grouping/associating heterogenous symbols.

I’d like to see a system that could handle any combination of heterogenous and homogenous symbols. (gEDA can handle it right now, but it is a manual process.) I’d also like to see the system handle parts that share pins. For example BAT54A, BAT54B, and BAT54C.

Ed

- Raw text -