Mail Archives: geda-user/2015/02/08/12:10:29
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.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -