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=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=I9xKYoDzxwqIeERyM4e19F9A2MPFWIvvIwSxv2r2N5E=;
        b=Azwyeh7UON+fei0JvscIAOsKZvU4GaUKSCR+vk2zYCeEhkMF/Ma8C89qN1SrdOZUND
         O73GZblb0aGO1kD2AsSkAsjGiKhZcvx7851/puhLt9T58+zbSDIpeXVItKCDVOe34KVs
         B1+nzC30KmcQh77SpJCr3DudWk7sXwe7H1/Uuk+PHnylam6rncPdDnXpKStFWSMJf+6j
         9O/LHRev1hNsyy/f0/OaiRKiVik9cTjoAneope/6KRGfj1X2kt2AEqV27Isx7VAyQKAs
         klh4OVnF8WJDN1gXPLNK4Hs5p47noP8eSQnq2eInf80lqYqa/A4xvszI6xwTJOhKxzyG
         DRug==
MIME-Version: 1.0
X-Received: by 10.50.43.202 with SMTP id y10mr987508igl.86.1443106931782; Thu,
 24 Sep 2015 08:02:11 -0700 (PDT)
In-Reply-To: <CAC4O8c8pjk_Z8A3fyk5QZ77TcBsGYFYOgCfgQQ6rEC-Hze_Lew@mail.gmail.com>
References: <alpine DOT DEB DOT 2 DOT 11 DOT 1509031356150 DOT 13201 AT nimbus>
	<msi77b$6rr$1 AT ger DOT gmane DOT org>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1509082036590 DOT 3066 AT lichen>
	<201509082040 DOT t88KerD6005455 AT envy DOT delorie DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1509091224440 DOT 3949 AT lichen>
	<201509091737 DOT t89Hb1nQ021026 AT envy DOT delorie DOT com>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509211409470 DOT 1633 AT newt>
	<20150921164548 DOT d9f1367e416d6a2e41b0a23a AT gmail DOT com>
	<CAC4O8c8pjk_Z8A3fyk5QZ77TcBsGYFYOgCfgQQ6rEC-Hze_Lew AT mail DOT gmail DOT com>
Date: Thu, 24 Sep 2015 08:02:11 -0700
Message-ID: <CAOP4iL1dMWeGE6ZX4fybKC2AQo1PvbKLkttmpOVp_mcc7Oz45w@mail.gmail.com>
Subject: Re: [geda-user] New experimental netlist features
From: "Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: multipart/alternative; boundary=089e011604ba0abeea05207f8476
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

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

On Wed, Sep 23, 2015 at 4:00 PM, Britton Kerin (britton DOT kerin AT gmail DOT com)
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

>
>
> On Mon, Sep 21, 2015 at 6:45 AM, Nicklas Karlsson (
> nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <
> geda-user AT delorie DOT com> wrote:
>
>> > ...
>> > So what you are criticize it the fact that I use buses and bus pins for
>> > "multiple nets" whereas you prefer to use non-bus nets and ordinary
>> pins?
>> >
>>
>> At least me think bus pins are really good idea.
>
>
> It sounds good to me that a bus would go with a bus pin.  I probably don't
> know all the considerations but that definitely sounds most simple from a
> first-encounter perspective.
>
> Britton
>
>

You have to deal with three situations. Single pins, multiple pins with the
same base name, and multiple pins with multiple  base names. Only the last
one is a bus. The second one
is a vector.

John Eaton

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Sep 23, 2015 at 4:00 PM, Britton Kerin (<a href=3D"mailto:britt=
on DOT kerin AT gmail DOT com">britton DOT kerin AT gmail DOT com</a>) [via <a href=3D"mailto:ged=
a-user AT delorie DOT com">geda-user AT delorie DOT com</a>] <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user 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"><div dir=3D"ltr"><b=
r><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><span class=3D"=
">On Mon, Sep 21, 2015 at 6:45 AM, Nicklas Karlsson (<a href=3D"mailto:nick=
las DOT karlsson17 AT gmail DOT com" target=3D"_blank">nicklas DOT karlsson17 AT gmail DOT com</a=
>) [via <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-use=
r AT delorie DOT com</a>] <span dir=3D"ltr">&lt;<a href=3D"mailto:geda-user AT delori=
e.com" target=3D"_blank">geda-user AT delorie DOT com</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">&gt; ...<br>
<span>&gt; So what you are criticize it the fact that I use buses and bus p=
ins for<br>
&gt; &quot;multiple nets&quot; whereas you prefer to use non-bus nets and o=
rdinary pins?<br>
&gt;<br>
<br>
</span>At least me think bus pins are really good idea.</blockquote><div><b=
r></div></span><div>It sounds good to me that a bus would go with a bus pin=
.=C2=A0 I probably don&#39;t know all the considerations but that definitel=
y sounds most simple from a first-encounter perspective.</div><div><br></di=
v><div>Britton</div><div><br></div></div></div></div></blockquote><div><br>=
<br></div><div>You have to deal with three situations. Single pins, multipl=
e pins with the same base name, and multiple pins with multiple=C2=A0 base =
names. Only the last=C2=A0 one is a bus. The second one<br></div><div>is a =
vector.<br><br></div><div>John Eaton<br>=C2=A0<br></div></div><br></div></d=
iv>

--089e011604ba0abeea05207f8476--