X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Ironport-SBRS: None
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2HoAwBTLKFX/52AA4Bdg0WBUq0KjCSBfYYdAoE/OBQBAQEBAQEBA1onQQ4BhA4BAQQBOkQLCxgJExIPBQ08E4gXAw8IBbsfDYNNAQEIAiWGKoRNgkOBWYNQgi8FjwuJdDSMSoIrj0mIK4QFg3ceNoQaHDKEc4F5gUUBAQE
X-IPAS-Result: A2HoAwBTLKFX/52AA4Bdg0WBUq0KjCSBfYYdAoE/OBQBAQEBAQEBA1onQQ4BhA4BAQQBOkQLCxgJExIPBQ08E4gXAw8IBbsfDYNNAQEIAiWGKoRNgkOBWYNQgi8FjwuJdDSMSoIrj0mIK4QFg3ceNoQaHDKEc4F5gUUBAQE
X-IronPort-AV: E=Sophos;i="5.28,463,1464678000"; 
   d="scan'208";a="31459812"
Date: Tue, 2 Aug 2016 16:33:04 -0700
From: Larry Doolittle <ldoolitt AT recycle DOT lbl DOT gov>
To: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] Wilkinson splitter - how to implement and use?
Message-ID: <20160802233304.GA2086@recycle.lbl.gov>
References: <23abdc31 DOT 72365e7a DOT 572529a9 DOT 212e2 AT o2 DOT pl>
 <a5562efe70ac4b83b066facd19a46167 AT gwp>
 <20160801162742 DOT GA27552 AT recycle DOT lbl DOT gov>
 <20160801184707 DOT 7b3dda2d3c0d13e103a5ec59 AT gmail DOT com>
 <a7acaf21-df0d-d209-d053-fcc470762ea3 AT ecosensory DOT com>
 <s6n60rkz3g8 DOT fsf AT blaulicht DOT dmz DOT brux>
 <201608012000 DOT u71K0pN2001967 AT envy DOT delorie DOT com>
 <CAHUm0tO1-ke5jcKsqYstiajENUis2f=nn5=jZkaNQ+HGDVg6zw AT mail DOT gmail DOT com>
 <CAM2RGhSxV=-czyN-vNRRzy8r1OErBcYSdT+uZ=-R86bsWyRcdg AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAM2RGhSxV=-czyN-vNRRzy8r1OErBcYSdT+uZ=-R86bsWyRcdg@mail.gmail.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
Precedence: bulk

Evan -

On Tue, Aug 02, 2016 at 04:47:05PM -0400, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> On Mon, Aug 1, 2016 at 6:44 PM, Erich Heinzle (a1039181 AT gmail DOT com)
> [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> > If pcb were modified to honour the flag, I could easily add a "nodrc" flag
> > as discussed to the non-pad line element outputs of the utility.
> I think we need something more subtle than nodrc. Having DRC turned
> off for a specific footprint or any other board area is just as bad as
> having DRC return bogus warnings/errors.

I agree in general.  For the copper structures wished for to handle
star grounds and Wilkinson splitters, we actually want the layer
to exist for DRC purposes, but not for netlist purposes.  So a
"nonetlist" flag?

> The reality is that these structures are not footprints but functional
> elements. They have design rules, just very different ones with higher
> orders of complexity. We can't really have pcb process the full
> complexity of these rules across the whole domain from DC to daylight
> (or shorter) because of limitations in processing. It would also
> require a level of developer time which is far past what pcb-* has
> right now.

Without diving into a more general capability set, this particular tweak
_sounds_ simple enough to me.  But my limited experience poking around in
the internals of the existing pcb code base makes me predict it will be
difficult to do without breaking somethings else.  Maybe I'll look at
pcb-rnd and see if that looks any more promising.

  - Larry