X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 X-Authenticated-UID: jpd AT noqsi DOT com Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] Net attributes From: John Doty In-Reply-To: <201507162123.t6GLNlqR029844@envy.delorie.com> Date: Thu, 16 Jul 2015 15:45:18 -0600 Message-Id: <27634B69-446A-4BA7-B05B-0F9436DF694F@noqsi.com> References: <20150712224637 DOT 2d4cc2de AT wind DOT levalinux DOT org> <55A2E9B7 DOT 9040502 AT neurotica DOT com> <20150713131707 DOT GA782 AT recycle DOT lbl DOT gov> <55A4042E DOT 5060402 AT neurotica DOT com> <55A41B30 DOT 50602 AT neurotica DOT com> <254F9AFE-1A3E-4D88-BABF-E6E0F87A56B1 AT icloud DOT com> <1436960577 DOT 1072 DOT 6 DOT camel AT ssalewski DOT de> <201507151820 DOT t6FIKYME001704 AT envy DOT delorie DOT com> <201507152007 DOT t6FK7lv8005229 AT envy DOT delorie DOT com> <24AD56C6-B7C2-4D7E-B69A-F68DBACCBFDC AT noqsi DOT com> <4DD9C29A-2105-45DC-9F17-82DA23433919 AT icloud DOT com> <55A7D999 DOT 5020101 AT ecosensory DOT com! ! ! > <74093FC3-C9AA-4AFF-A158-720676E70E49 AT noqsi DOT com> <201507162045 DOT t6GKj06r028442 AT envy DOT delorie DOT com> <8F26D2B2-3724-4264-B8A4-933E9377306D AT noqsi DOT com> <201507162123 DOT t6GLNlqR029844 AT envy DOT delorie DOT com> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t6GLjPZo017947 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 Jul 16, 2015, at 3:23 PM, DJ Delorie wrote: > >> Nope. I sometimes have to make multiple copies of a subcircuit >> schematic: same topology but different components. Having more >> control over hierarchy expansion in gnetlist would be good. > > I was thinking about the m4 problem in pcb and thought "I wonder if we > could put a generic expression parser in where we expect simple > values". I don't think it would help much for pcb (without a looping > construct, at least), but it might help for heirarchical schematics if > a component could have a value that was an expression referencing > inherited attributes from the parent. Inherited attributes would be nice. Needs a new mechanism in code few understand, though. > The schematic flattener (if > you're flattening it for netlisting, for example) would expand the > expression. > > Part of me says "put a guile expression there" but that opens up the > problem of having a schematic with executable code in it. I’ve considered, for similar purposes, making a tiny recursive top-down interpreter for ordinary arithmetic expressions in Guile. Such things are not difficult to write. That would keep the executable code genie in the bottle. > Given the > nature of electronics, a mathematical (TeX? Mathematica?) expression > would be more natural, but bring its own can of worms… > If you’re specifying discrete part values, one tricky issue is specifying the catalog of acceptable values. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com