X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Sun, 12 Feb 2017 21:01:13 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] gnetlist chaos
In-Reply-To: <1365AFCF-15FC-4222-8C33-AC75D1DAAB29@noqsi.com>
Message-ID: <alpine.DEB.2.11.1702122039590.31724@nimbus>
References: <D0E30DB4-3ADF-415C-A95E-B58F09AE054D AT noqsi DOT com> <alpine DOT DEB DOT 2 DOT 11 DOT 1702111609100 DOT 25113 AT nimbus> <CAJXU7q_ogjTmEOjruGJ3od-GYdv_gef0X_yc7Fne1q6kDu1xrg AT mail DOT gmail DOT com> <20170212090109 DOT GA450 AT localhost DOT localdomain> <alpine DOT DEB DOT 2 DOT 11 DOT 1702121039420 DOT 2050 AT nimbus>
 <20170212102807 DOT GB30751 AT localhost DOT localdomain> <alpine DOT DEB DOT 2 DOT 11 DOT 1702121203520 DOT 2781 AT nimbus> <20170212122649 DOT GD11686 AT localhost DOT localdomain> <alpine DOT DEB DOT 2 DOT 11 DOT 1702121538030 DOT 2881 AT nimbus> <1365AFCF-15FC-4222-8C33-AC75D1DAAB29 AT noqsi DOT com>
User-Agent: Alpine 2.11 (DEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-1793232069-1486929673=:31724"
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

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1793232069-1486929673=:31724
Content-Type: TEXT/PLAIN; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8BIT

On Sun, 12 Feb 2017, John Doty wrote:
> On Feb 12, 2017, at 8:19 AM, Roland Lutz <rlutz AT hedmen DOT org> wrote:
>> If your intention is to have a better Scheme API or a way to invoke the 
>> netlisting functionality from Scheme, just build on the current version 
>> of gEDA/gaf.  It allows you to do so really easily.
>
> Frome a Schemer point of view, the trouble with gnetlist is that the 
> actual data structures are hidden behind an FFI. You have a different 
> FFI, but that doesn’t solve the fundamental problem.

If you mean from the Scheme side, then it's the same FFI.  If you mean 
from the Python side, then things are really different because both the 
code accessing the netlist data and the netlisting code live in the same 
interpreter.  This means that e.g. a backend has access to *all* the 
information the netlister has; it is basically part of the same thing.

Since the Scheme API is separate from the netlist data, you can just 
change it in any way you like, or define your own API and load it into the 
netlister.  You could use xorn/src/python/geda/netlist/guile.py as a 
starting point.

Do you have any special information in mind which you would want to 
access?

--8323329-1793232069-1486929673=:31724--