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=VcmrjDXdH3XoPgvT6PUeTaaoDd8Hc+4tfz7cKtex7Xg=;
        b=SD14tL7Xg4J03PeN0aFQ72sZFNiKL/GXI/p8tFp1iuJtOMFWeeuwHbR9/+EsN+5QXW
         THFWRU7BYZcZt68mVh1yzANxb+bwE0qfBC+aPOvdJojRpAxpY7orGoUHoG3TFOPATBwp
         VOdCoA5LaRmzcwVHsDwfh2aSzk73NX+/qtuVGuW3uSSfGW8reoKZeHd4En/NDiW01xK9
         SM6L/iSI1FIGjopb8KE01p873+HO3XboDH5v5/2XL99A3+gtTakcC9twSpJ2dA/UHzoM
         pninunPWiOP1emOAwRueIi7qqh3ZYNCLeR2S+yANFCv3XFqq47aSszzqK1i6rwNwCK4y
         501Q==
MIME-Version: 1.0
X-Received: by 10.107.162.7 with SMTP id l7mr4492726ioe.20.1423440900660; Sun,
 08 Feb 2015 16:15:00 -0800 (PST)
In-Reply-To: <52E0C8E3-2FD3-4D79-A01D-962E7EFA6D4F@noqsi.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>
Date: Sun, 8 Feb 2015 15:15:00 -0900
Message-ID: <CAC4O8c9xVaJh=dioU6_nTcfVQPaSzzD-QS8Qy+rbRRo_zX=Xbg@mail.gmail.com>
Subject: Re: [geda-user] Using Lua to safely read configuration and layout
 files (program attached)
From: Britton Kerin <britton DOT kerin AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t190F6Qf024541
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 Sun, Feb 8, 2015 at 8:09 AM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Feb 8, 2015, at 9:41 AM, Chris Smith <space DOT dandy AT icloud DOT com> wrote:
>
>>
>>> On 8 Feb 2015, at 15:53, John Doty <jpd AT noqsi DOT com> wrote:
>>>> On Feb 8, 2015, at 6:39 AM, Christian Riggenbach <criggenbach AT magahugu DOT ch> wrote:
>>>
>>>> Simple
>>>> tasks like outputing the filenames of all the referenced symbols should be
>>>> possible with the netlister,
>>>
>>> Yes. However, that information is hidden by the API. The Scheme configuration code tells the C layer where to look. The C layer finds the files. The C layer does not reveal the file names, or where it found them, through the API to the Scheme layer. This is a problem. Similarly, you can attach attributes to net segments, but the netlister can’t get at them. Having the schematic representation in C structures and only publishing certain views of this data through the Scheme API is a serious limitation. The views are well chosen for flat netlisting and BOM generation, but sometimes you need more.
>>
>> Yes! And that's the main point to using Lua for the data format. The data file _is_ the internal representation.
>
> In Lua’s representation. Not as a Scheme data structure. You have exactly the same problem the C implementation has: you must expose the data through a Scheme API. You’re not really solving any problems, just torquing the design to fit your Lua prejudice.

+1+1+1.  In advocating the use of a less-known language that you personally
happen to know, you're essentially saying that your prospective contributions
are larger than the prospective contributions of a much larger community.
You might be right but the odds are against it.  The languages themselves
aren't different enough for the differences to matter.

Britton