X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Mon, 16 Jan 2017 21:09:47 +0100 (CET) From: Roland Lutz To: "Svenn Are Bjerkem (svenn DOT bjerkem AT googlemail DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] gEDA/gaf: want an advice In-Reply-To: Message-ID: References: <20170115211156 DOT GB27077 AT localhost DOT localdomain> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-1752142486-1484597388=:1482" 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 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1752142486-1484597388=:1482 Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Mon, 16 Jan 2017, Svenn Are Bjerkem (svenn DOT bjerkem AT googlemail DOT com) [via geda-user AT delorie DOT com] wrote: > can we have real buses in gschem? We already have that: just check out the branch 'xorn-experimental' in the geda-gaf repository. Here is an excerpt from the original announcement mail: > Components can now have bus pins. […] The "pinnumber=" attribute on a > pin and the "netname=" attribute on a bus are interpreted as a > comma-separated list of pin ranges. Pin ranges can be denoted by either > ".." or ":"; when using the latter notation, the last pin isn't included > in the list. Optionally, the pin range can be given in brackets and > have a common prefix. > > Examples: "4..7,14..11" -> 4 5 6 7 14 13 12 11 > "D[8:0]" -> D7 D6 D5 D4 D3 D2 D1 D0 > > Bus rippers still work the way they did before (i.e., not at all unless > you set the appropriate attributes by hand). I didn't merge this feature into master yet because there didn't seem to be a consensus on what a bus should be. Given that the feature has been requested several times since, it may be a good idea to merge it anyway, though. --8323329-1752142486-1484597388=:1482--