X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=gamma;
	h=date:from:to:subject:message-id:references:mime-version
	:content-type:content-disposition:in-reply-to:user-agent;
	bh=fSKwHJ54MpcrWnCpd0UdxeMZgufrEf4kwXUDGcfixy8=;
	b=r/JJ+dPIl/IzohHDoXvQwLlKptTGvmUsNe4GA8NBlzZTvgRuCCNRK8r5WGdCkIWlLC
	uALw87RecjXK9FTxJVoEvGZOCoXt3ZgzqP0OvNGEFdTAbWWBOjRne5N7fVYSV4alrlvR
	/0mjFvnuXMdIhw+Fk309r9Gn6H8il0Btrn1Pk=
Date:	Tue, 8 Nov 2011 19:00:40 +0100
From:	Cyril Hrubis <metan DOT lists AT gmail DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] duplicate refdes values
Message-ID:	<20111108180039.GA6472@yumi>
References:	<20111108100616 DOT GA32119 AT yumi>
	<89AF1CB2-6703-4ABC-A43D-7EA37559426F AT noqsi DOT com>
MIME-Version:	1.0
In-Reply-To:	<89AF1CB2-6703-4ABC-A43D-7EA37559426F@noqsi.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)
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

Hi!
> > I've got bitten by this once more and decided for fix. The problem is
> > that I've, by a mistake, forgot to change refdes on one of my resistors
> > and spend another ten minutes by figuring out what went wrong.
> > 
> > What I want to fix is that both gsch2pcb and pcb are silent about this
> > and the pcb just picks up only one of them.
> > 
> > As far as I understand the gsch2pcb source it acts as a stream editor
> > and has no memory of previous parts I was thinking of adding hash table
> > of previous refdes values and make it print warning on duplicate
> > entires. I could prepare patch for this.
> > 
> > The pcb is more compliacted though both by the source code and by a gui
> > perspective. 
> 
> 1. This has nothing to do with pcb: this is gnetlist's normal behavior.
 
Well both of the tools keep silent about this which is in my opinion
wrong.

> 2. This is not a bug, it is a feature. Duplicate refdes values are the
> way you express the fact that you are treating a single single
> physical device as broken into several sections.

I'm saying this is a bug, I'm saying that this is worth a warning. What
about warning about duplicated refdes for syms that has no slotting
defined?

> 3. The drc2 back end to gnetlist already complains about duplicated
> refdes values for non-slotted components. Checking a design for errors
> is what drc2 is for, and if you're not using multiple heterogeneous
> symbols for parts, drc2 will do what you want here. The problem is
> that this isn't necessarily an error: this is one of the many cases
> where drc2's model of design is narrower than the capabilities of the
> toolkit. In this case, it is hard to fix drc2, as the indications of
> true error (inconsistent pin connections) are hidden behind the
> unnecessarily opaque gnetlist back-end API.

Sorry, I don't understand this one. Is drc2 any kind of tool? 

-- 
Cyril Hrubis

- Raw text -