X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Sun, 25 Oct 2015 00:24:00 -0400 Message-Id: <201510250424.t9P4O0ZB017263@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: (geda-user AT delorie DOT com) Subject: Re: [geda-user] Star shorts References: <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> <20151024050756 DOT GA5741 AT recycle DOT lbl DOT gov> <201510240528 DOT t9O5S5qc019927 AT envy DOT delorie DOT com> Reply-To: geda-user AT delorie DOT com It occurs to me that we could, perhaps just for testing, use the net *name* to flag its functionality. For example: netname=D0.bus netname=D1.bus netname=D2.bus . . . netname=TP.matchl netname=TM.matchl Etc. That's something that PCB can read *now* and a plugin DRC could check for. I don't think "star" applies to a net, it's what goes *between* nets.