X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Fri, 6 Feb 2015 19:44:47 +0100 (CET) X-X-Sender: igor2 AT igor2priv To: geda-user AT delorie DOT com X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu" From: gedau AT igor2 DOT repo DOT hu Subject: Re: [geda-user] FOSDEM In-Reply-To: Message-ID: 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> <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> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 Precedence: bulk On Fri, 6 Feb 2015, John Doty wrote: > > On Feb 6, 2015, at 9:29 AM, Jason White wrote: > >> For those who have not seen, I implemented an example program in C >> using Lua to safely read data defined in Lua files. > > And that is of little use. The schematic and configuration files need to be trivially readable/writable by *any* language that the tool maker chooses (AWK, perl, Python, ObjectiveC, ?). The geda-gaf schematic format is already excellent from that perspective. Guile configuration files are less satisfactory. Formats tied to a specific language implementation are not a good idea. I agree. Another aspect of the same thing: ideally, the cost of implementing importers, exporters or filters should be low, independelty of the language the user picks. When this works, the cost is either equally hard or equally easy. If we go for the easy parsing, the language should be small and simple. A turing complete scripting language is usually not the smallest or simplest approach. a subset of such a language is better, but may still be too feature-rich. Unless you assume everyone will use a lua interpreter... 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? Regards, Igor2