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=Pm0gNRYVoh1tcQIO+WBBchByqyGwSopZnajoLQMFaQM=;
        b=O5ej7azunN/1lWRdKyTQydRTb4nVE+l6zktj4nfUWslQJtkuVh1EFx1BOkhXgbai0E
         0D3mtUwTDE6B4DsejIx4zxM3oaNFz2+BMfj8JOM+FyA8kbHMhrSiEi6sYYOO8mr7L2om
         d2wGWKvtAtr89AMmqC+AUkpR+wcuNmWpYTd9e8igCtA+tyV5jme77QN0rhewAxFxdtYw
         JM5VZY0XgYrlmUGIibtvcVaSzyWV6LXOZA2pXk1DSm2PVg3VHD9WLqUflRJtwX1kR/EP
         lOUFWuBn+gfObl/y0AJ34TKWQ3mZFFOIT6rzE69o6JoIfrpOXqS1k0ENJhX5HpPvdXB1
         K7BA==
MIME-Version: 1.0
X-Received: by 10.112.146.2 with SMTP id sy2mr15098201lbb.104.1445754342267;
 Sat, 24 Oct 2015 23:25:42 -0700 (PDT)
In-Reply-To: <201510250424.t9P4O0ZB017263@envy.delorie.com>
References: <CAM2RGhQhNkShqtN8uyCSd7R+V4FgLXDZTvTC2RTdmKF7C_8ndA AT mail DOT gmail DOT com>
	<201510220136 DOT t9M1a5Uw015222 AT envy DOT delorie DOT com>
	<CAM2RGhQOpnBXbZXngNq=RcQTZN=UrU+PGzTZ9AC=xKNfu_zQkQ AT mail DOT gmail DOT com>
	<201510220149 DOT t9M1nrIe016145 AT envy DOT delorie DOT com>
	<CAM2RGhQ26+gpcAeTdgJpBEh0egOGLYcpizQ+B6kfTQLowEk5xQ AT mail DOT gmail DOT com>
	<20151022023002 DOT GA25952 AT recycle DOT lbl DOT gov>
	<CAM2RGhQ7xfMDe1knmiFkW8MAZ4Sr=ZSas8Ca9Sadv3gJT2z3gw AT mail DOT gmail DOT com>
	<201510221643 DOT t9MGhFfg003310 AT envy DOT delorie DOT com>
	<20151022170259 DOT GA28154 AT recycle DOT lbl DOT gov>
	<CAC4O8c-AGwV59t6-K+73eaZt0d43bJe0kE8E68n9pWxaa9gP+Q AT mail DOT gmail DOT com>
	<20151024050756 DOT GA5741 AT recycle DOT lbl DOT gov>
	<201510240528 DOT t9O5S5qc019927 AT envy DOT delorie DOT com>
	<CAM2RGhTh0zk0JNhq00D0aRbaY9_a7ZBAAo_n=igOt13E4D5-0Q AT mail DOT gmail DOT com>
	<201510250424 DOT t9P4O0ZB017263 AT envy DOT delorie DOT com>
Date: Sun, 25 Oct 2015 06:25:42 +0000
Message-ID: <CAM2RGhScar6LDyzsCtne+xpA--A0NE_bfUKas=XMBaqaUvfkwQ@mail.gmail.com>
Subject: Re: [geda-user] Star shorts
From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: gEDA users mailing list <geda-user AT delorie DOT com>
Content-Type: text/plain; charset=UTF-8
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 Sun, Oct 25, 2015 at 4:24 AM, DJ Delorie <dj AT delorie DOT com> wrote:
>
> It occurs to me that we could, perhaps just for testing, use the net
> *name* to flag its functionality.  For example:
>
>        netname=D0.bus
>        netname=D1.bus
>        netname=D2.bus
>        . . .
>
>        netname=TP.matchl
>        netname=TM.matchl
>
> Etc.  That's something that PCB can read *now* and a plugin DRC could
> check for.
>
> I don't think "star" applies to a net, it's what goes *between* nets.

I like the simplicity but I see some issues. Granted I am kind of high
right now one hierarchical nets.

What if you have more than one bus? You just labeled stuff as part of
a bus but not which one. You need to pass some other information. I
guess if you like doing it that way you could with yet another period.
I also think that if you did that it would break a few of the backends
which right now ignore my additional attribute.

The nice thing about what I was describing is that it it let you put a
scope on things. There are times when I would like to make ground or
power rail on a page be in a star with out having to use a special
symbol with the correct number of pins or the mess of netlines that
would require. The special symbol thing just seems clumsy to me.

Granted star is a property of the node and not the net but there are
times when I want to make a specific pin the center of a star for a
limited region of a net. What I was describing handled that nicely
with out having it expand to the whole rest of the net. We can't do
that with netname=GNDA.star if we stick with flattened netlists. The
same goes for having a symbol that is the center of the star there is
no way to make cleanly convey that that star symbol is actually a pin
on some other symbol. If you hide the attribute name on my example the
visible text is a minor amount of visual clutter and still carries the
message.

PCB is just one end point for this. I would rather solve the gschem /
gnetlist part first and then deal with PCB later. With PCB-RND the
mainline of PCB is no longer the only target for our output. (Doty
would point out it never really was anyway.)

-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/