Mail Archives: geda-user/2015/02/08/10:54:33
On Feb 8, 2015, at 6:39 AM, Christian Riggenbach <criggenbach AT magahugu DOT ch> wrote:
> I once wanted to change a netlister backend to my needs, but I gave up and
> used grep/awk/cut because of the (IMHO) obscure syntax of scheme.
Obscure syntax? Hardly, it’s just parentheses. It’s the functions in the parentheses that are obscure ;-)
> 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.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -