X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] New experimental netlist features
Date: Sun, 06 Sep 2015 22:20:58 +0200
Lines: 73
Message-ID: <msi77b$6rr$1@ger.gmane.org>
References: <alpine DOT DEB DOT 2 DOT 11 DOT 1509031356150 DOT 13201 AT nimbus>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: a89-182-144-163.net-htp.de
User-Agent: KNode/4.14.1
Reply-To: geda-user AT delorie DOT com

Roland Lutz wrote:

> - Components with a single pin can now have a "netname=" attribute
> which acts like a "net=" attribute on that pin.  This allows using
> the "netname=" attribute as a clean label on customizable power
> symbols.

Finally! :-)
The colon was a crutch which had an astonishingly long life.


> - Analogously, I/O ports in subschematics can now be indicated using
> the "portname=" attribute instead of "refdes=".  If there are I/O
> ports for which there is no matching pin in the instantiating
> symbol, an error is reported.

This obsoletes the "overloading" of the refdes attribute. I always 
found this a crutch.


> - Components can now have bus pins.  This is currently only
> available by hacking the file (i.e., changing the next-to-last
> number in the pin line from "0" to "1").  The "pinnumber=" attribute
> on a pin and the "netname=" attribute on a bus are interpreted as a
> comma-separated list of pin ranges.  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?

> 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.

 
> - 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? 


> - A subsheet symbol can have one ore more "subst=NAME=VALUE"
> attributes. Inside the subschematic, any occurrence of "$(NAME)" is
> replaced with "VALUE".

Great!
This makes sub sheets more versatile. E.g. a filter with 


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


> in particular, it isn't possible to change slotting or
> subsheet source files this way.

Fair enough.
Parametrized slotting might have been a nice tool, though. 
Parametric subsheets would have opened whole can of worms. How would 
you prevent infinite rekursion? 

Again, thank you for the good work!

---<)kaimartin(>---