X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=JWOi/pkRcowvOFUnP/hQkNTb1tPRCsoSWcACnX0+wGI=; b=spdBu1io2U9u2MVNyfmulepwXhBY7TECS+Vpkc/eg36jrlBZbtwMYp3EbGr8CWZjbU iwxB80NTspaMa081FxGieaUS7g6pmy3pIsluLDE5d1IQxVmRmC3NBWjebwQUeMWnmjNq q3VttVmQBfyofD4idGjnkZz4KsY3CzUz7pqCybETpHUwmsxvrUeF5IfI7EDLLivI1fH7 uYntfYZlEVCiIGMVIkIs4cZP0yg4ceW65zfnRY03R5H3SjCo6gzOCmH2R/5pHTXHUsHW 7BuYl07f5qDCbz6bkjxPIHLLHliYt/L+hSYpKHa3sCT+hThMVNaZXe34KUChlNXwnCiZ j3ag== X-Received: by 10.194.250.40 with SMTP id yz8mr66418906wjc.37.1441829765301; Wed, 09 Sep 2015 13:16:05 -0700 (PDT) Date: Wed, 9 Sep 2015 22:16:00 +0200 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] New experimental netlist features Message-Id: <20150909221600.bf87d8962b781f3751cad244@gmail.com> In-Reply-To: References: <20150908233235 DOT b6cde3ec6c40bf235a7a1df8 AT gmail DOT com> <201509082144 DOT t88LiOXW007712 AT envy DOT delorie DOT com> <201509082355 DOT t88NtdSM012317 AT envy DOT delorie DOT com> <201509091721 DOT t89HL4iS020376 AT envy DOT delorie DOT com> <20150909212022 DOT e0d7ed9a6eac110f71c1787c AT gmail DOT com> <201509091921 DOT t89JLiWa025041 AT envy DOT delorie DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 > > On 9 September 2015 at 21:21, DJ Delorie wrote: > > Ok, but *you* get to write the parser for it :-) > > > > Are we talking about parsing the target languages, or are we talking about a bundle notation which the back-ends can translate? > > > My opinion of what we’re talking about (although I may be wrong). If the target netlist language doesn’t support busses (most cases) we expand the bus to nets in the netlister. The netlister provides a function to do this. If the bus notation of the target netlist language matches our notation, we pass it through untranslated. For extra credit, translate our bus notation to a different target bus notation. This sounds like a very good idea. I assume a net must have the same name in all ends of the bus and. For a net connected to one bus the bus name could simply be added before the net name but for a net connected to several buses?