X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7+dev X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: inbox From: "karl AT aspodata DOT se [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] lepton netlist In-reply-to: References: <20240424112803 DOT C0DAC81AB8A3 AT turkos DOT aspodata DOT se> Comments: In-reply-to "=?utf-8?Q?Stephan_B=C3=B6ttcher?= (geda AT psjt DOT org) [via geda-user AT delorie DOT com]" message dated "Wed, 24 Apr 2024 14:41:11 +0200." Mime-Version: 1.0 Content-Type: text/plain Message-Id: <20240424134027.DA8B681AB8A3@turkos.aspodata.se> Date: Wed, 24 Apr 2024 15:40:27 +0200 (CEST) X-Virus-Scanned: ClamAV using ClamSMTP 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 Stephan: > I do not know any guile. My patch was in C, but the attachment points > were moved to scheme, I guess. Yes, your file s_hierarchy.c doesn't exist any more. It is mentioned in commit 597b38ef193d4249e74fea04c131af078bd9ccd5. > I do remember that somebody implemented similar functionality, but I do > not remember which fork that was. From what I remember geda has it, unfortenatly I cannot compile it here. geda commit c7ed6c5a10cbfba3001b6b2e55bbc3ed0f1e84b8 is probably what I remember. ... > My patch was doing simple text substitutions in attributes after the > hierarchy was built, so the parameters cannot effect the netlist > itself, just some output. I used it only with value= attributes. That > would be the minimal functionality. So, it would be the bom list and the like that would be affected ? In that case an external program could do the transform, so you do your usual stuff and then as a final step you modify some output files with a separate program. Would that be fine (at least till it is integrated into lepton) ? > Something that can also affect, e.g., source= attributes may be quite a > bit more intrusive. What is the idea with that ? Regards, /Karl Hammar