X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=05Ro5Sks9pd7egIsG/xX77CsQKsqtFgz5iTTOpZQ0tw=;
        b=lkDxAsv1XBxfeaM1M5vvQEo2nH7XZAKnmmf3yHabncL1WF66ovUfC/gzCQnsJjBWZp
         zjsFQ8h+8s/5RwE7bGY2Yjrduvny3VCMwo04p0usqYFIGKtipvoJlVgXakhJ8bmZeB4U
         4x6Auscn2LY4Bcm+XCow2L3FJFD54cifvvtqDZv+QVVuqO5Md8+i1gXVaQV+IKSzohTY
         W7E8qjJmndAUzkSzSW9vElNj+6OtQO2b9AJixBUW1KIgYiuPSsAgUNjOV26O62hC0q9c
         24bTJ0HLD+uavOTBgN8h/pYdFf6JHvU0CASel89fGIHc5du+iLUUaKuyjF83mXt1Nk0j
         L2KA==
MIME-Version: 1.0
X-Received: by 10.52.233.164 with SMTP id tx4mr296321vdc.65.1414012399082;
 Wed, 22 Oct 2014 14:13:19 -0700 (PDT)
In-Reply-To: <201410221952.s9MJqSKc008045@envy.delorie.com>
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>
	<201410221952 DOT s9MJqSKc008045 AT envy DOT delorie DOT com>
Date: Wed, 22 Oct 2014 22:13:19 +0100
Message-ID: <CA+cauMADpGFMsaVhs234YW3rs7x2gybcU4Jan-VcEnnGk8ssEA@mail.gmail.com>
Subject: Re: [geda-user] Is someone using busses in gschem?
From: Alexis Phoenix <alexis DOT happyphoenix AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=089e011849c4c160010506096ad1
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

--089e011849c4c160010506096ad1
Content-Type: text/plain; charset=UTF-8

I've used busses which do affect the netlist, in another program and
they're really useful. When I go back to gschem (now I undersand cad more!)
netlist busses would certainly be appreciated here. In the other program
(DesignSpark) you just connect your nets to/from the bus wherever you like,
it by default labels them with the net-names, and they are processed as
individual nets.

On 22 October 2014 20:52, DJ Delorie <dj AT delorie DOT com> wrote:

>
> > So current gschem busses are only a visual guide of connectivity,
> > with no impact to netlist.
>
> Right.  Busses have nothing to do with netlists.
>

--089e011849c4c160010506096ad1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ve used busses which do affect the netlist, in anoth=
er program and they&#39;re really useful. When I go back to gschem (now I u=
ndersand cad more!) netlist busses would certainly be appreciated here. In =
the other program (DesignSpark) you just connect your nets to/from the bus =
wherever you like, it by default labels them with the net-names, and they a=
re processed as individual nets.<br></div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On 22 October 2014 20:52, DJ Delorie <span dir=3D"=
ltr">&lt;<a href=3D"mailto:dj AT delorie DOT com" target=3D"_blank">dj AT delorie DOT com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><=
br>
&gt; So current gschem busses are only a visual guide of connectivity,<br>
&gt; with no impact to netlist.<br>
<br>
</span>Right.=C2=A0 Busses have nothing to do with netlists.<br>
</blockquote></div><br></div>

--089e011849c4c160010506096ad1--