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-07_01:2015-02-07,2015-02-07,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=3 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1502070110 Sun-Java-System-SMTP-Warning: Lines longer than SMTP allows found and wrapped. From: Chris Smith Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (1.0) Subject: Re: [geda-user] FOSDEM Message-id: <9A55A675-2F17-4D11-A07C-D9F091B1ADD1@icloud.com> Date: Sat, 07 Feb 2015 11:08:48 +0000 References: <1420499386 DOT 3521 DOT 3 DOT camel AT cam DOT ac DOT uk> <20150203112631 DOT 3507a0c1 AT Parasomnia DOT thuis DOT lan> <20150204054256 DOT Horde DOT Pm1JV8RJbICk9SHvIGwZ7A3 AT webmail DOT in-berlin DOT de> <20150204193720 DOT Horde DOT 42xUN-NzhCJRWZne-M5eCQ1 AT webmail DOT in-berlin DOT de> <90236728-E79D-47C7-BFB1-34140DB85ACB AT sbcglobal DOT net> <201502042333 DOT t14NX28o024789 AT envy DOT delorie DOT com> <7C1A5871-3056-482C-BC58-173D90D80F77 AT icloud DOT com> <0BB497A3-1B7E-41FD-A6A3-935EB1259DD9 AT icloud DOT com> In-reply-to: To: "geda-user AT delorie DOT com" X-Mailer: iPad Mail (12B466) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t17B8wo3025049 Reply-To: geda-user AT delorie DOT com > On 7 Feb 2015, at 10:24, gedau AT igor2 DOT repo DOT hu wrote: > > Would I write my own XML parser? In some extreme situation absolutely yes^1. In other situations, no. Would I like if some "interchange format" was designed from ground up assuming one way or the other, effectively making the decision instead of me? Absolutely no. And this is where our views differ, you prefer to use a lib and you are willing to make decisions that would make it harder for other developers to do their part in a non-lib way. > > Writing a full xml parser is hard, because the language is large. I believe a full lua parser would not be too easy either. To me it seems lua syntax is much more complex (and powerful) than what I would think is needed for describing a schematics or a footprint or a PCB. The more extra features it has over the minimum, the more effort it is to implement a correct parser. I would like to say more on this, but lack the time right now. For the moment I will just say that you are mistaken: our views are actually the same. The Lua syntax is very simple and easy to parse without the Lua library. As I said in another email one of the primary use cases for Lua is configuration and data files, so it is intentionally easy to parse - it even has a few syntactic niceties to /help/ parsing, such as allowing a list to end with a dangling comma, e.g list = { 1, 2, 3, }. Chris