X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Mon, 7 Dec 2020 13:49:17 +0100 (CET) From: Roland Lutz To: Glenn , "Glenn (glimrick AT epilitimus DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] SAB processing patches In-Reply-To: <475f980e-fddd-60d1-9a02-a5bc5fb5805b@epilitimus.com> Message-ID: References: <20201130220505 DOT 0AE4282C54FD AT turkos DOT aspodata DOT se> <7c75ed03-456c-b408-8b50-0448f6b3a04f AT epilitimus DOT com> <1b2c64b3-6a36-c1f3-dd54-bb583c6bea17 AT epilitimus DOT com> <475f980e-fddd-60d1-9a02-a5bc5fb5805b AT epilitimus DOT com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) 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 Hi Glenn, I have a few questions about your patch series: - You introduce "sim" (for simulation) and "ab" (for PCB) as predefined contexts but state that user-defined contexts could be used, as well. What kind of user-defined context would make sense with this system? - In what kind of situation would you want to use the "bypass" action? - In what kind of situation would you want to use an external script, and what kind of modification would it do on the netlist? - What is the "order" parameter used for? - What does the patch to "s_slot.c" / the code in "sab.c" do? On Wed, 2 Dec 2020, Glenn (glimrick AT epilitimus DOT com) [via geda-user AT delorie DOT com] wrote: > If I understand correctly what you are describing could be done with an > SAB exec script. It wouldn't be formalized but it could be accomplished. > Kind of the whole impetus for SAB was to move the modification stage out > of the backends making it backend independent. What is your incentive to do this? > What header do I need to include to use the _() translation bit in C > code? I can't find it. This would be #include "libgeda_priv.h" for libgeda code and #include "gschem.h" for gschem code. Also, I missed one thing before: All C source files must have #include as their first include since other headers may define different things depending on macros define here. Roland