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: <544EAB40.8060505@ecosensory.com> Date: Mon, 27 Oct 2014 15:29:52 -0500 From: John Griessen User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] Is someone using busses in gschem? References: <1413980823 DOT 1391 DOT 1 DOT camel AT ssalewski DOT de> <201410221838 DOT s9MIcOFM005839 AT envy DOT delorie DOT com> <1414007359 DOT 1391 DOT 3 DOT camel AT ssalewski DOT de> In-Reply-To: <1414007359.1391.3.camel@ssalewski.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 10/22/2014 02:49 PM, Stefan Salewski wrote: > But I am not fully convinced that editing busses is really easier > than drawing some plain lines I think the essence of busses is not graphical, but an orderly list of names in a format that the netlister can use and makes sense in terms of thinking of the netlist. We've been talking about verilog-ams for the hierarchic netlist, but anything with similar buss names with numerical suffixes such as data_out[0:9] would be a good intermediate.