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:52:53 +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: <CAOFvGD5pOt4b1KsLeddCjZgEoefOVTnD5+YtN_m99mwqMkxrvw@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1502061945180.7324@igor2priv>
References: <1420499386 DOT 3521 DOT 3 DOT camel AT cam DOT ac DOT uk> <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> <A661E96B-1D00-43E8-9C5E-549FBAC7AB6A AT sbcglobal DOT net> <CAOFvGD5pOt4b1KsLeddCjZgEoefOVTnD5+YtN_m99mwqMkxrvw AT mail DOT gmail 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, Jason White wrote:

> On Fri, Feb 6, 2015 at 1:07 PM, Edward Hennessy <ehennes AT sbcglobal DOT net> wrote:
>>> On Feb 6, 2015, at 9:07 AM, John Doty <jpd AT noqsi DOT com> wrote:
>>>> On Feb 6, 2015, at 9:29 AM, Jason White <whitewaterssoftwareinfo AT gmail DOT com> 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
>> <snip>
>> Additionally, it becomes more difficult to create a GUI to edit the data when the data uses a complex file format.
>>
>> I'd prefer simple configuration and data file formats and save the languages for extensions.
>
> What is more simple than name=value or name={value, value, value}? I
> do no see how that is any more difficult to parse than the current
> format.

What is a value? Can it be an expression, even as simple as 1+1?

If yes, users will start depending on that feature and any importer will 
need to implement a compatible expression eval. After that, does it 
support (local) variables, constants or other shorthands?

If not, then we are walking the way that restricts the user to a very 
small subset of the language. If we do that, what's the advantage chosing 
a subset of lua for the purpose other than cheaper importer/exporter in 
lua (or embedded lua interpreter)? Just asking because the same argument 
works for any other data language or programming language that can be 
restricted in io.

At the end of the day, I find the "easier to handle in one specific 
language" or "easier to handle using a specific library" arguments weaker 
than the "easy to parse using a random language" argument.

Regards,

Igor2