X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-CMAE-Analysis: v=2.4 cv=ZIsSJV3b c=1 sm=1 tr=0 ts=5fd4019e a=+cj0cO56Fp8x7EdhTra87A==:117 a=nrn57TgB2vMNiriMJUfUNw==:17 a=9+rZDBEiDlHhcck0kWbJtElFXBc=:19 a=8nJEP1OIZ-IA:10 a=zTNgK-yGK50A:10 a=Ca784PVMEIYMLvjnGwIA:9 a=wPNLvfGTeEIA:10 X-SECURESERVER-ACCT: glimrick AT epilitimus DOT com Subject: Re: [geda-user] SAB processing patches To: geda-user AT delorie DOT com References: <1b2c64b3-6a36-c1f3-dd54-bb583c6bea17 AT epilitimus DOT com> <475f980e-fddd-60d1-9a02-a5bc5fb5805b AT epilitimus DOT com> <25887669-D8C1-48B8-BEE7-13EEBFC4D006 AT noqsi DOT com> <7f074abb-e7ae-275c-ee49-d06fc7f2a706 AT epilitimus DOT com> <836e84ad-aa1d-fa56-5996-7445d92e94db AT epilitimus DOT com> <1BBAE111-8895-4DD9-A10C-EB35019A6D93 AT noqsi DOT com> <0297F731-15CC-489C-9D2A-05A4C24F2DE3 AT noqsi DOT com> <5c2f1d66-7cb0-065f-2e88-06966f563580 AT epilitimus DOT com> <94FAF440-FEA2-4C98-81CF-D3E314487FB3 AT noqsi DOT com> From: "Glenn (glimrick AT epilitimus DOT com) [via geda-user AT delorie DOT com]" Message-ID: <657223b6-69d0-7ba8-66dc-97ab2c097538@epilitimus.com> Date: Fri, 11 Dec 2020 15:32:29 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.3 MIME-Version: 1.0 In-Reply-To: <94FAF440-FEA2-4C98-81CF-D3E314487FB3@noqsi.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - a2plcpnl0121.prod.iad2.secureserver.net X-AntiAbuse: Original Domain - delorie.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - epilitimus.com X-Get-Message-Sender-Via: a2plcpnl0121.prod.iad2.secureserver.net: authenticated_id: glimrick AT epilitimus DOT com X-Authenticated-Sender: a2plcpnl0121.prod.iad2.secureserver.net: glimrick AT epilitimus DOT com X-Source: X-Source-Args: X-Source-Dir: X-CMAE-Envelope: MS4xfPWUy3EZZ6b+IzB4WEIL44WRAZL12N+5qJ6wwXrJo+NN/I1DT8jFBliKUgbXS29LenNmEl2Gj5l8sO1Po0CVM3VtpU0j5f+XN480xOIvd7CDhPFuDe4U FrLdPea0c0r0zBwiRbArkdzffceqWQuQRQaa2oQZU9vUftaMy0feNO/1yED2fybRRWuu/fd/LJmKFe5E5M6HznOzKeUZ2Hn97U4JflbfXjO1BV2giFtdrjM8 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 John Doty wrote: > >> >>  Anything more complex is handled >> via an external user specified script accessed through the 'exec' >> action.  > > How is this different from what the -l and -m options to gnetlist and > lepton-netlist do? > 1. I can't speak re: lepton-netlist. As currently written gnetlist only uses the -l and -m  switches when using -g not with -p (Roland: correct me if I am wrong on this, but that is how I read the code). 2. -l and -m only allow scheme scripts while SAB works with python scripts. 3. SAB annotation is at the component level. So ideally SAB activated scripts are more task specific and hence more reusable. 4. SAB annotations are listed in the schematic (hopefully) making it clearer what is being done and under what conditions. 5. SAB allows processing branches to be mixed and matched as needed without modifying other files. This can be done with -l/-m using something like makefiles and bundling scripts but with SAB that isn't needed. 6. SAB activated scripts receive a clearly defined set of parameters upon which to operate. I don't know enough about the scheme side to know how this is handled there. 7. SAB doesn't have an analog of -m, it works solely between netlist generation and backend processing. Glenn