X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Thu, 8 Jul 2021 20:25:00 +0200 (CEST) From: Roland Lutz To: geda-user AT delorie DOT com Subject: Re: [geda-user] Thank you - some requests and an offer In-Reply-To: <516720E8-7097-4943-89FB-EB0F53B38AD1@noqsi.com> Message-ID: References: <20210707101437 DOT 2c7c63a6 AT queeg> <516720E8-7097-4943-89FB-EB0F53B38AD1 AT noqsi 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 On Thu, 8 Jul 2021, John Doty wrote: > On Jul 8, 2021, at 9:11 AM, Roland Lutz wrote: > > For anyone even a bit familiar with Python, this lowers the entry > > barrier for writing custom backends tremendously. > > Not true. Xorn *raised* the barrier for me. I see it as an extra layer > of obfuscation beyond the normal obfuscation of using an OO approach for > an essentially functional job. Well, if you think netlist generation is a "functional job" and disagree with the object-oriented approach in the first place (leave alone Python), then I'm not terribly surprised that you aren't happy with that. For anyone else, just have a look at the folder of Guile netlist backends, pick one, and see if you can tell what's going on. Then compare this to the corresponding Python backend: http://git.geda-project.org/geda-gaf/tree/gnetlist-legacy/scheme http://git.geda-project.org/geda-gaf/tree/xorn/src/backend I think this speaks for itself.