Mail Archives: geda-user/2017/02/12/15:25:59
--Apple-Mail=_5D006FCE-CD96-4781-98C2-947F38C9B51C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
On Feb 12, 2017, at 1:01 PM, Roland Lutz <rlutz AT hedmen DOT org> wrote:
> 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.
>>=20
>> 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=92t solve the fundamental problem.
>=20
> 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.
>=20
> 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.
>=20
> Do you have any special information in mind which you would want to =
access?
What Vladimir has been doing is *eliminating* the FFI, so that all of =
the functions and data are Scheme. That makes everything more =
transparent, so your question becomes moot. What you=92ve done is to =
substitute a different opaque data storage layer, so you still need the =
FFI. Maybe better for Pythonians, but Vladimir=92s approach is better =
for Schemers.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_5D006FCE-CD96-4781-98C2-947F38C9B51C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJYoMR+AAoJEF1Aj/0UKykRPNsQAIMCcAODzQFmG56A8HSzPN/3
msTft+hjNn6pPvGIjoTyL8Tw3mfAukH+LuRY8sLWMR3d94aKLbz8BsTdNHIrmke6
RA2QF/nICIfHDYSCguObAlyrOgK4BLKhAzk8vpXQsdPrUPthkSeaaTgi4J79vU7x
LNDSR31dN/j2v/fIBgHuqK39+nBJvnZwKyhkHNKjnhn7aBigoOau6PcALGgyMF5+
b9HBR+JMuVfFHxiL0rL79Fnvtm8PRu4oXhjslng4TwTMYm83745bSjViKz4CJuTi
yogDIdswh3wkTToeGBwnuItRa71lvWEcVXPFWCF4EPlzdlW9ibIozACJgNO7Xb8S
1rvZIwciXyKI7c6VHEoGKOtHvaHVkgj+l/rNWGKXtt2MwW9QzJFl58M5MCposgmA
gTA23/ViUdKC55IAxSyxMWEXp+gRf9Jw5/KW0ocLjG3t9/pR0Ot5d6X/POtgjIRC
kn3KrieIOxYOUJJklKIp7ua2y4b9chDyxYVUo/vGZq507cdp55pnQH+Hsci8fHxZ
wNYtOTf0r/qBPk7z8mkmikesVu/UFjpk/8M55hYBf2js+5v2qfnabS8G+5giUKmJ
tqMSoXQDh6ipLUEVB03Qi698AowzLyfY4pW+wsIlNbmDU28UWNRXYRgAMmaHlk8D
ELAz9fHYlkZXgOMyVV4h
=1Pjf
-----END PGP SIGNATURE-----
--Apple-Mail=_5D006FCE-CD96-4781-98C2-947F38C9B51C--
- Raw text -