X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Virus-Status:	Clean
X-Virus-Scanned:	clamav-milter 0.98.4 at av02.lsn.net
Message-ID:	<54E342B2.8000500@ecosensory.com>
Date:	Tue, 17 Feb 2015 07:31:30 -0600
From:	John Griessen <john AT ecosensory DOT com>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version:	1.0
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] Star connection points in PCB?
References:	<1502170242 DOT AA18887 AT ivan DOT Harhan DOT ORG>
In-Reply-To:	<1502170242.AA18887@ivan.Harhan.ORG>
Reply-To:	geda-user AT delorie DOT com

On 02/16/2015 08:42 PM, Spacefalcon the Outlaw wrote:
> Now as far as actually implementing starpoint support in PCB, I'm
> thinking of the following approach: find the code that checks for
> shorts, and work the hack in there: teach the code that for certain
> pairs of nets declared in some way, having exactly*one*  short is
> fine, but having two or more shorts is bad - and having no short at
> all is bad too for those special nets.  But I might be totally off-
> base here, not having looked at the code at all yet.

The concept of a star point is fine, but saying there can be only one short depends on where.
Allowing multiple connections or loops to itself in a power net is often what you
get when overlapping parts of thick layout tracks, so you want to allow that.

How about the case where your start point handles three power nets?
You want to allow that also.

So I don't see a way to have the program do that step for us.  (The
step of enforcing "no loops in power nets")

John

- Raw text -