X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Proofpoint-Virus-Version:	vendor=fsecure
	engine=2.50.10432:5.13.68,1.0.33,0.0.0000
	definitions=2015-02-09_01:2015-02-09,2015-02-08,1970-01-01 signatures=0
X-Proofpoint-Spam-Details:	rule=notspam policy=default score=0 spamscore=0
	suspectscore=5 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0
	reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1502090096
MIME-version:	1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject:	Re: [geda-user] Using Lua to safely read configuration and layout
	files (program attached)
From:	Chris Smith <space DOT dandy AT icloud DOT com>
In-reply-to:	<54D7CC55.1090602@ecosensory.com>
Date:	Mon, 09 Feb 2015 09:04:49 +0000
Message-id:	<5D8980D1-7456-476C-80B5-9FB01E8530AE@icloud.com>
References:
	<CAOFvGD7pJTo8A=MXVbuuXO=++0vGukUyqVfckVtnCi99ziqWJQ AT mail DOT gmail DOT com>
	<3709636 DOT NVszrDDjOR AT jasum> <20150208135925 DOT 6f6ddab6 AT Parasomnia DOT thuis DOT lan>
	<1897145 DOT BbSdS1MRWc AT jasum> <EE929E31-B2C7-48BF-BA49-B2E728DB99C3 AT noqsi DOT com>
	<66DD3BF9-092C-4EFF-B12D-6214141C152D AT icloud DOT com>
	<52E0C8E3-2FD3-4D79-A01D-962E7EFA6D4F AT noqsi DOT com>
	<C26D592D-04B1-4AB0-9F32-6D5A537EBAF4 AT icloud DOT com>
	<638942CE-E278-40ED-8C36-6A89C33FD158 AT noqsi DOT com>
	<CAGde_xM8Gfs-xAQad33h2d9aTTWV7e4Cyegw6A-Wbs+phP5scQ AT mail DOT gmail DOT com>
	<54D7CC55 DOT 1090602 AT ecosensory DOT com>
To:	geda-user AT delorie DOT com
X-Mailer:	Apple Mail (2.2070.6)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t1995bL3008300
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

> On 8 Feb 2015, at 20:51, John Griessen <john AT ecosensory DOT com> wrote:
> 
> On 02/08/2015 12:54 PM, Svenn Are Bjerkem wrote:
>> I can't help myself asking: Why isn't the gnetlist code exposing the needed information to the API? Too difficult to do, or too
>> boring to get done?
>> 
> 
> It must be the temperament of those that decide to spend time on the project.
> 
> a.  Too boring to do.
> b.  Requires too much slogging for too little braggable results.
> c.  Does not pay well.
> d.  It's a large enough task that some cooperation would be a great help, but it's hard to find any...
> e.  "Where to start?"  *AND*  "I don't like writing documentation."
> 
> Just my guesses.

No, I just think it’s the inherent problem with domain-specific parsers and interpreters.  Those things were not implemented simply because the author didn’t envisage a need for them.  That’s the advantage of generic, structured file formats like XML or Lua: any parser or interpreter must be complete, because there is no way of predicting what may or may not be useful.  The advantage of picking a format which is also native to a language, like Lua, means that scripting and manipulation of that data is also much easier, because there no need for a secondary parser or interpreter.

Chris

- Raw text -