X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Mon, 19 Jun 2017 14:24:17 +0200 (CEST)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "Anton Dubniak (twister AT tfsoft DOT org DOT ua) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] Parameter substitution --> hierachy
In-Reply-To: <614f7601eb62dc51d8b416c313c939f8@tfsoft.org.ua>
Message-ID: <alpine.DEB.2.20.1706191414250.12595@nimbus>
References: <98D1C4E4-581D-4A03-94E4-E0330960EADF AT wellesley DOT edu> <s6na8h89ydi DOT fsf AT blaulicht DOT dmz DOT brux> <alpine DOT DEB DOT 2 DOT 11 DOT 1607231941050 DOT 16188 AT nimbus> <s6n8tws1428 DOT fsf AT blaulicht DOT dmz DOT brux> <alpine DOT DEB DOT 2 DOT 11 DOT 1607232257250 DOT 1800 AT nimbus> <s6npoq4x9bx DOT fsf AT blaulicht DOT dmz DOT brux>
 <EA4BA0F4-6B70-4C17-B801-2BE99AB48AE8 AT noqsi DOT com> <s6nmvl7x6h6 DOT fsf AT blaulicht DOT dmz DOT brux> <20160724090420 DOT fc7353ebc390b8f46bb5ebfc AT gmail DOT com> <614f7601eb62dc51d8b416c313c939f8 AT tfsoft DOT org DOT ua>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
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, 18 Jun 2017, Anton Dubniak (twister AT tfsoft DOT org DOT ua) [via 
geda-user AT delorie DOT com] wrote:
> What was the agreement reached (if any) on the problem of parametrical 
> subcircuits?
>
> Any plans to implement this in mainline gEDA/gaf or Lepton EDA?
>
> I will gratefully test the relevant code (like this patches 
> https://bugs.launchpad.net/geda/+bug/911440) in my projects if there 
> will be at least a hint about the direction towards which this feature 
> will be developed.

gEDA/gaf supports parameter substitution for subschematics since February.

To add a parameter to a subschematic, add an attribute with the name 
"param" and a value of the form "NAME=VALUE" to each instantiating 
component.  Each occurrence of "$(NAME)" inside the subschematic will be 
replaced with "VALUE".

This works for any attribute value retrieved by a netlist backend.  If you 
need to change something else parametrically (e.g., an attribute name), 
please contact me.

Roland