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 av01.lsn.net Message-ID: <55EF7C26.8080108@ecosensory.com> Date: Tue, 08 Sep 2015 19:24:06 -0500 From: John Griessen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] New experimental netlist features References: <201509082040 DOT t88KerD6005455 AT envy DOT delorie DOT com> In-Reply-To: <201509082040.t88KerD6005455@envy.delorie.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 09/08/2015 03:40 PM, DJ Delorie wrote: > No reason to not support a list/range in pinnumber= (or pinlabel=) > though. > > pinnumber=5,6,8,9 > > the netlister could match that up with netname=D[0..3] And the same is true for nets or busses, which are same thing just more nets is a buss. If a buss is labelled [0..3] and is in contact with a buss having label x[0..31] all the info is there to figure out that the [0..3] buss is called x[0..3]