X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Wed, 23 Sep 2015 00:31:09 +0200 (CEST) From: Roland Lutz To: geda-user AT delorie DOT com Subject: Re: [Geda-developers] PLEASE STOP !!! - Re: [geda-user] Apollon In-Reply-To: <945CF17D-0840-4208-90D4-DA423B7E7133@noqsi.com> Message-ID: References: <20150917043146 DOT GA1837 AT localhost DOT localdomain> <20150917142035 DOT GA5896 AT localhost DOT localdomain> <56018A8B DOT 6010000 AT jump-ing DOT de> <945CF17D-0840-4208-90D4-DA423B7E7133 AT noqsi DOT com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) 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 Tue, 22 Sep 2015, John Doty wrote: > Gschem and gnetlist are old, complex programs that nevertheless have > great flexibility. No individual user or developer really understands > all of their capabilities. In the process of refactoring gnetlist, I grokked it thoroughly. (IOW, I don't think there is an aspect of gnetlist which I don't understand. This doesn't apply to the backends, though.) > The potential for inadvertent harm when modifying them is great. This is why I was very careful when porting gnetlist to Python/Xorn, and treated porting and refactoring as two strictly separate steps. The first version of the netlister which I posted on this list was ported, but almost not refactored; the resemblance to gnetlist was much closer.