X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Sat, 11 Feb 2017 18:23:30 +0000
From:	"Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] gnetlist chaos
Message-ID:	<20170211182330.GO21523@foo.stuge.se>
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>
	<0D03FED9-A309-4F6C-9863-0EC6DB35176D AT noqsi DOT com>
MIME-Version:	1.0
In-Reply-To:	<0D03FED9-A309-4F6C-9863-0EC6DB35176D@noqsi.com>
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

John Doty wrote:
> > > It’s based on a completely new foundation (“xorn”: don’t ask me what that is or what it does, it’s very murky to me).
> > 
> > Probably best to look at what it is before passing comment.
> 
> I have.  I can’t make sense of it.  It seems to be a peculiar
> custom OO framework for a job that isn’t naturally OO.

The significant difference with xorn is that it allows treating
the various existing objects which exist in the gEDA data model
for a long time in a structured way, from C, Python and other
languages.

There is nothing inherently object-oriented about the xorn C code,
but in Python the gEDA objects are indeed Python objects, because
that makes sense.


> as far as I can tell, nobody else understands it well enough to
> write a back end, unlike gnetlist proper.

How do you think that could change?


//Peter

- Raw text -