Mail Archives: geda-user/2017/02/12/15:03:17
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--
- Raw text -