X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Thu, 22 Oct 2015 15:53:03 -0400 Message-Id: <201510221953.t9MJr3Hp013618@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: <20151022213200.c3f45fb3723dbcef555df7b9@gmail.com> (geda-user AT delorie DOT com) Subject: Re: [geda-user] A lesson from gnet-makefile References: <201510220112 DOT t9M1Ccfq013731 AT envy DOT delorie DOT com> <201510220136 DOT t9M1a5Uw015222 AT envy DOT delorie DOT com> <201510220149 DOT t9M1nrIe016145 AT envy DOT delorie DOT com> <20151022023002 DOT GA25952 AT recycle DOT lbl DOT gov> <201510221643 DOT t9MGhFfg003310 AT envy DOT delorie DOT com> <20151022170259 DOT GA28154 AT recycle DOT lbl DOT gov> <20151022213200 DOT c3f45fb3723dbcef555df7b9 AT gmail DOT com> 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 > There should be exactly one short at the star ground point. If > algorithm calculate their lines meet at the edge end point have to > checked in some way. Or if a particular bit of copper could be tagged as "star point" or something, the algorithm could know that it should be the edge of multiple nets, and verify it. I'm just thinking, our DRC isn't designed to handle these types of problems, but a new DRC might, and give us other benefits too.