Mail Archives: geda-user/2015/02/07/00:41:06
An alternate idea is to have symbol and footprint files that are
parseable templates (lua, m4, perl, cobol, whatever floats your boat)
with different file suffixes (dip14.fp.lua, sot34.fp.m4,
THIS_IS_A_RESISTOR.FOOTPRINT.COBOL, etc). The trick is to figure out
a way to apply the correct interpreter to the template when read,
along with providing whatever parameters/attributes the interpreter
might need (i.e. a DIPn.fp.perl script where <n> is provided by the
netlist).
Once read in, there's no reason to keep computed values/patterns as
expressions, and we don't want the *stored* data to require a specific
interpreter, although I can see the value of having attributes being
expressions (parameterizable simulations, etc).
- Raw text -