X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sat, 7 Feb 2015 00:39:57 -0500
Message-Id: <201502070539.t175dv9Q029508@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <14b62812151.e34558b378672.554006307999274698@zoho.com> (message
	from ryanseal on Sat, 07 Feb 2015 00:31:28 -0500)
Subject: Re: [geda-user] FOSDEM
References: <1420499386 DOT 3521 DOT 3 DOT camel AT cam DOT ac DOT uk> <20150202152654 DOT GA13336 AT cuci DOT nl> <54CFD589 DOT 9040702 AT xs4all DOT nl> <CAHBYzfRkn-nJb4JfrDYyaD0WwPrpZvAgi0QdHCusgz185iNoHA AT mail DOT gmail DOT com> <CAGde_xN-iNZUvHh-E47kx1EyoPRt1018wWiDwHhYQ9+od+cJwA AT mail DOT gmail DOT com> <20150203112631 DOT 3507a0c1 AT Parasomnia DOT thuis DOT lan> <20150204054256 DOT Horde DOT Pm1JV8RJbICk9SHvIGwZ7A3 AT webmail DOT in-berlin DOT de> <CAOP4iL2stWVCy3WK0=SNu2zAbs8t6B0uyAgFuOnzG8v_MrYNfw AT mail DOT gmail DOT com> <CAGde_xN5gs5r_on=HP2RN7cy6E=2EL9eK3cp+sd9BfBaWNLVew AT mail DOT gmail DOT com> <20150204193720 DOT Horde DOT 42xUN-NzhCJRWZne-M5eCQ1 AT webmail DOT in-berlin DOT de> <90236728-E79D-47C7-BFB1-34140DB85ACB AT sbcglobal DOT net> <CAOFvGD4M48Ap=UQzL_T3yzas2rJrNFfxXRUOkOe8gA8J3bQCHg AT mail DOT gmail DOT com> <201502042333 DOT t14NX28o024789 AT envy DOT delorie DOT com> <7C1A5871-3056-482C-BC58-173D90D80F77 AT icloud DOT com> <CAOFvGD7vdircWqDYWKrKPY49gpYo4ZGsw20q9yE+4+gno3ZkhA AT mail DOT gmail DOT com> <F66800B5-AAC3-459C-B6BC-B2F1E4AC98CC AT noqsi DOT com> <14b62812151 DOT e34558b378672 DOT 554006307999274698 AT zoho DOT com>
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


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).