X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type:content-transfer-encoding;
	bh=0kB45x+088xYvDYgcPbNrkmDVbmkGSxV3zL+liHGwzo=;
	b=pFwen3wsIQKrDaziES1s2Oj/Rr+G8W5UnbMl7BGwa3Q743qdGPQnwKugcADzzgb+IY
	KY9t3Fdryn02jXwOeNCbplixXM28UGE5e847wogaJojr7mE23eQW3jMOkmRm6uwyKobT
	ekBmCUHCvCoxPt5UoIm53tmUaMc90ijDWVYZ9ynMTi9aa7G2rgbfdZ2dPAqxP4nC7ASi
	/3j/uXU7HBgrHczwbij5roPBvQsGNvydo60FoRVuHTQy8s2v1r1fJqyXua6mRjc8n3cz
	UW5sdZQumkMu0ISL+Rjun/PYJjHNAqz0rVTslqX4W0nN15U4CeqvKSSzXQPzXc//EKYt
	pBXw==
MIME-Version:	1.0
X-Received:	by 10.50.25.225 with SMTP id f1mr8510376igg.29.1423335091703; Sat,
	07 Feb 2015 10:51:31 -0800 (PST)
In-Reply-To:	<0BB497A3-1B7E-41FD-A6A3-935EB1259DD9@icloud.com>
References:	<1420499386 DOT 3521 DOT 3 DOT camel AT cam DOT ac DOT uk>
	<20150202152654 DOT GA13336 AT cuci DOT nl>
	<54CFD589 DOT 9040702 AT xs4all DOT nl>
	<CAHBYzfRkn-nJb4JfrDYyaD0WwPrpZvAgi0QdHCusgz185iNoHA AT mail DOT gmail DOT com>
	<CAGde_xN-iNZUvHh-E47kx1EyoPRt1018wWiDwHhYQ9+od+cJwA AT mail DOT gmail DOT com>
	<20150203112631 DOT 3507a0c1 AT Parasomnia DOT thuis DOT lan>
	<20150204054256 DOT Horde DOT Pm1JV8RJbICk9SHvIGwZ7A3 AT webmail DOT in-berlin DOT de>
	<CAOP4iL2stWVCy3WK0=SNu2zAbs8t6B0uyAgFuOnzG8v_MrYNfw AT mail DOT gmail DOT com>
	<CAGde_xN5gs5r_on=HP2RN7cy6E=2EL9eK3cp+sd9BfBaWNLVew AT mail DOT gmail DOT com>
	<20150204193720 DOT Horde DOT 42xUN-NzhCJRWZne-M5eCQ1 AT webmail DOT in-berlin DOT de>
	<90236728-E79D-47C7-BFB1-34140DB85ACB AT sbcglobal DOT net>
	<CAOFvGD4M48Ap=UQzL_T3yzas2rJrNFfxXRUOkOe8gA8J3bQCHg AT mail DOT gmail DOT com>
	<201502042333 DOT t14NX28o024789 AT envy DOT delorie DOT com>
	<7C1A5871-3056-482C-BC58-173D90D80F77 AT icloud DOT com>
	<CAOFvGD7vdircWqDYWKrKPY49gpYo4ZGsw20q9yE+4+gno3ZkhA AT mail DOT gmail DOT com>
	<F66800B5-AAC3-459C-B6BC-B2F1E4AC98CC AT noqsi DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1502061931470 DOT 7324 AT igor2priv>
	<0BB497A3-1B7E-41FD-A6A3-935EB1259DD9 AT icloud DOT com>
Date:	Sat, 7 Feb 2015 09:51:31 -0900
Message-ID:	<CAC4O8c_WfS_EESygiaREDtMn0kbKDhMeUhf6ccYVnhHDPKe=rw@mail.gmail.com>
Subject:	Re: [geda-user] FOSDEM
From:	Britton Kerin <britton DOT kerin AT gmail DOT com>
To:	geda-user AT delorie DOT com
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t17Ipahr014706
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 Fri, Feb 6, 2015 at 11:39 PM, Chris Smith <space DOT dandy AT icloud DOT com> wrote:
>
>> On 6 Feb 2015, at 18:44, gedau AT igor2 DOT repo DOT hu wrote:
>>
>> So the question is: what's the smallest C or python or awk or whatever non-lua program you can write that can parse the file _without_ depending on a lua interpreter? And how far can it go supporting the user exploiting lua features?
>
> What is the problem with depending on a Lua interpreter? Please bear in mind that we're not talking about a behemoth like Python or PERL here, with numerous dependencies and files scattered over the system. Lua is a single C library with a simple API, about 50kB in size that can be statically linked if you want. Bindings to other languages of choice are available.
>
> I think Lua is being skewed in people's minds by the terms 'script' and 'interpreter'. In use Lua behaves much more like an XML or YAML library.

Its yet another minority language that few people know.  There aren't enough
benefits to using it for it to be worth it.  If you aren't going to be using
the executable features, there's no reason not to use something more widely
known and supported.  That means YAML or JSON.  YAML is more readable and
allows cross-refs, JSON is probably more common and has more parsers available.

Britton

- Raw text -