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-08_03:2015-02-08,2015-02-08,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-1502080194 From: Chris Smith Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (1.0) Subject: Re: [geda-user] Using Lua to safely read configuration and layout files (program attached) Message-id: Date: Sun, 08 Feb 2015 17:44:45 +0000 References: <3709636 DOT NVszrDDjOR AT jasum> <20150208135925 DOT 6f6ddab6 AT Parasomnia DOT thuis DOT lan> <1897145 DOT BbSdS1MRWc AT jasum> <66DD3BF9-092C-4EFF-B12D-6214141C152D AT icloud DOT com> <52E0C8E3-2FD3-4D79-A01D-962E7EFA6D4F AT noqsi DOT com> In-reply-to: <52E0C8E3-2FD3-4D79-A01D-962E7EFA6D4F@noqsi.com> 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 t18Hise5019369 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 8 Feb 2015, at 17:09, John Doty wrote: > >> On Feb 8, 2015, at 9:41 AM, Chris Smith wrote: >> 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. I had thought getting rid of Scheme was one of the design goals, and in my view that is solving a problem. :) Joking aside, the issue is that the gschem format isn't native to any language, and anything that uses it must parse it for it to be of any use. Any application parser (as shown by the netlister) is usually incomplete, because it's considered a waste of effort to parse features that you don't think people will want and it's difficult to predict how people will use it. By using a well defined format like Lua, /everything/ is parsed and made available because it /has/ to be. Am I biased towards Lua? Yes, I'll admit that, but only because I have researched this before and wholeheartedly believe it is the right tool for the job. Chris