X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sat, 16 Jan 2016 18:26:16 -0500
Message-Id: <201601162326.u0GNQGr7003843@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <A640C2D0-3C1D-41F2-BA7C-C599EFE30789@noqsi.com> (message from
	John Doty on Sat, 16 Jan 2016 16:19:47 -0700)
Subject: Re: [geda-user] first attempt at bus support in gnetlist for pcb
References: <201601080714 DOT u087Ejj5032766 AT envy DOT delorie DOT com> <F723B760-53BB-467C-8595-20EB5FC50E47 AT noqsi DOT com> <201601161959 DOT u0GJxa4G027544 AT envy DOT delorie DOT com> <0E73A3F8-8B1B-4C2A-9792-766AA724905D AT noqsi DOT com> <201601162211 DOT u0GMB1E4032505 AT envy DOT delorie DOT com> <A640C2D0-3C1D-41F2-BA7C-C599EFE30789 AT noqsi DOT com>
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


> > I think my [] syntax could be made nestable, and expanded to include
> > <> or () pairings.  Perhaps the netlister could auto-wrap everything
> > in a sub-circuit, then expand everything back up.
> 
> Not quite sure what you mean here. The back end and plug in have no
> control of hierarchical expansion.

I mean even a non-bus net like "Vcc" could become <Vcc> in the
sub-circuit, resulting in A4/<Vcc> -> A4/Vcc.  It's a "list of one",
instead of requiring the user to manually <> things that are lists of
more-than-one.

Whether that's done by the backend, plugin, or core, doesn't matter.