kicad-developers team mailing list archive

["Lorenzo" <lomarcan@...>]

--- In kicad-devel@xxxxxxxxxxxxxxx, Dick Hollenbeck <dick@...> wrote:

> (footprint footprint_def
> (units mil)
> (resolution 10)
> (const variable_def 30.4)
> (padstack pad_def ......)
> (pad pin1 pad_def 0 0 (expr 0 + variable_def * 0))
> (pad pin2 pad_def 0 0 (expr 0 + variable_def * 1))
> (pad pin3 pad_def 0 0 (expr 0 + variable_def * 2))
> (pad pin4 pad_def 180 250 (expr 0 + variable_def * 0))
> (pad pin5 pad_def 180 250 (expr 0 + variable_def * 1))
> (pad pin6 pad_def 180 250 (expr 0 + variable_def * 2))
> (pad pin7 pad_def 180 250 (expr 0 + variable_def * 3))
> (outline....)
> 
> # we should probably support comments, and teach the
> # lexer to pass them up to the parser so they can be preserved.
> )

Put I in PN and you've got a scheme dialect :D well, use SIOD or guile to not reinvent the wheel of course...

Otherwise LUA could be fun too... (a pascaloid designed for data definition... it is a python concurrent, too:P). The data domain of course is different but there is a worked example here:

http://www.lua.org/pil/10.1.html