X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Authenticated-IP:	207.224.51.38
Mime-Version:	1.0 (Apple Message framework v1084)
Subject:	Re: [geda-user] duplicate refdes values
From:	John Doty <jpd AT noqsi DOT com>
In-Reply-To:	<20111108192007.GF6940@yumi>
Date:	Tue, 8 Nov 2011 12:35:08 -0700
Message-Id:	<8E356312-1B25-4281-B7AB-518934785F7A@noqsi.com>
References:	<20111108100616 DOT GA32119 AT yumi> <89AF1CB2-6703-4ABC-A43D-7EA37559426F AT noqsi DOT com> <20111108180039 DOT GA6472 AT yumi> <201111081833 DOT pA8IXpek012142 AT envy DOT delorie DOT com> <20111108190803 DOT GE6940 AT yumi> <201111081915 DOT pA8JFD0X013781 AT envy DOT delorie DOT com> <20111108192007 DOT GF6940 AT yumi>
To:	geda-user AT delorie DOT com
X-Mailer:	Apple Mail (2.1084)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id pA8JZEon014139
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 Nov 8, 2011, at 12:20 PM, Cyril Hrubis wrote:

> Okay, so warning on duplicate refres with overlaping pins?

Multislot components with explicit power, like dual-opamp-1.sym in the library, will trigger such an objection. Overlapping pins with different nets attached would be a more robust indicator of trouble. This impinges on the the somewhat difficult question of shorted nets in a schematic: under what conditions are they allowed, and how should the gnetlist front end communicate their names to the back end?

In any case, detecting any sort of pin overlap will require a change in the gnetlist front end, where you will encounter difficult code guarded by hostile gatekeepers.

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

- Raw text -