X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 X-Authenticated-UID: jpd AT noqsi DOT com Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] Using Lua to safely read configuration and layout files (program attached) From: John Doty In-Reply-To: <66DD3BF9-092C-4EFF-B12D-6214141C152D@icloud.com> Date: Sun, 8 Feb 2015 10:09:06 -0700 Message-Id: <52E0C8E3-2FD3-4D79-A01D-962E7EFA6D4F@noqsi.com> 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> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t18H9CUT016221 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 Feb 8, 2015, at 9:41 AM, Chris Smith wrote: > >> On 8 Feb 2015, at 15:53, John Doty wrote: >>> On Feb 8, 2015, at 6:39 AM, Christian Riggenbach 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. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com