X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Tue, 8 Sep 2015 22:21:15 +0200 (CEST)
From:	Roland Lutz <rlutz AT hedmen DOT org>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] New experimental netlist features
In-Reply-To:	<msi77b$6rr$1@ger.gmane.org>
Message-ID:	<alpine.DEB.2.00.1509082036590.3066@lichen>
References:	<alpine DOT DEB DOT 2 DOT 11 DOT 1509031356150 DOT 13201 AT nimbus> <msi77b$6rr$1 AT ger DOT gmane DOT org>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version:	1.0
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

On Sun, 6 Sep 2015, Kai-Martin Knaak wrote:
>> Pin ranges can be denoted by either ".." or ":"; when using the latter 
>> notation, the last pin isn't included in the list.
>
> what is the benefit of the ":"-format?

I'm not a fan of notations where the first and last included element are 
mentioned; but I realize some users might want to use such a format, so I 
allowed typing "0..7" instead of "0:8".

>> Bus rippers still work the way they did before (i.e., not at all
>> unless you set the appropriate attributes by hand).
>
> So the party to celebrate the arrival of working buses in gschem will
> have to be postponed until after the next code sprint.

The main reason I didn't implement bus rippers is that I couldn't come up 
with a convincing way they should work that offers a significant advantage 
to the current state.  How exactly do you think bus rippers should work?

>> - Subschematics can now have I/O busses.  I/O bus pins work
>> analogously to normal bus pins but have a "pinlabel=" attribute
>> instead of a "pinnumber=" attribute.  Inside the subschematic, you
>> can either use a matching I/O port symbol with a bus pin or
>> individual net port symbols.  Bus I/O ports currently only support
>> the new "portname=" syntax.
>
> Not sure what this is about.
> Can you give a use case and/or an example?

You can use bus pins on subschematic symbols.  For an example, see the 
file "tests/netlist/mod_7seg.sch" in the branch "experimental".

>> This only works for attribute retrieval from
>> packages;
>  ^^^^^^^^
> symbols? What would be a package in this context?

The set of symbols with a given refdes.  Parameter substitution works when 
getting the "device" attribute of "R1"; it doesn't work when getting the 
"device" attribute of slot 1 of "R1".

BTW: I noticed there is a "change pin type" menu item in gschem, so you 
can actually create bus pins without hacking the file.

Roland

- Raw text -