X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Fri, 14 Dec 2012 05:21:51 +0100 (CET)
X-X-Sender: igor2 AT igor2priv
To: geda-user AT delorie DOT com
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] Find rat lines
In-Reply-To: <898C7D41-7B55-4D61-9CC6-7ABB560C144E@noqsi.com>
Message-ID: <alpine.DEB.2.00.1212140517080.26605@igor2priv>
References: <20121204183305 DOT 6b04c0dc AT jive DOT levalinux DOT org> <20121208112649 DOT 388a9d22 AT jive DOT levalinux DOT org> <1355011808 DOT 19390 DOT 8 DOT camel AT localhost> <alpine DOT DEB DOT 2 DOT 00 DOT 1212090407031 DOT 26605 AT igor2priv> <1355188647 DOT 12937 DOT 14 DOT camel AT localhost> <A7B4EDBD-3704-4837-9350-A16559C60A2A AT noqsi DOT com>
 <1355442697 DOT 2993 DOT 14 DOT camel AT localhost> <008677C3-7BA0-4B7D-B8E7-D0A5B2CCC573 AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1212140350530 DOT 26605 AT igor2priv> <898C7D41-7B55-4D61-9CC6-7ABB560C144E AT noqsi DOT com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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



On Thu, 13 Dec 2012, John Doty wrote:

> <snip> But but for finding an incidental short, "the least number of traces" 
> is a heuristic. There's no guarantee that those are the correct traces 
> to break.

Hah, I have an even better idea. I know you won't read the full thread, 
not even my summary and/or won't try very hard to understand the point 
about using histry (tagging or not) and what to do when that's not 
available.

Instead, write down how this specific feature would _exactly_ work in your 
dream PCB. You don't need to write code and you don't need to describe any 
more feature than needed to understand how you would resolve shorts. Then 
I will try to show you cases on which it doesn't work (there will be cases 
as your approach can't read the mind of the user either). I suspect these 
cases would be similar to the ones where the history based approach breaks 
(be it true history or tagging).