X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=EGqjA2ER0d58TTCDSwmev8NgpcY46Z6OKv3RMjPqETQ=; b=FTzryuGrnPuuN6mcS5j6YvXCdWPHcSUwLOtDP1T+CNvTCv2/lCZ0j0znUCjKuo8FSp sgg4tNVO5eVnaXe+VPAoWRWVV6T/zjVxd3sDZdVW2vzJ++T1pl3vDhJDZ1Fv/der8jkz NaEEkr6dwc3p9GzzG1i+5WaVqAkKHd1pI4GsnrjxnytGAIoPsa3xRHvdAW9rzQ4/cUMh oD3y+bQYaLpyQSf+koFCjlRhv1Ex9AIOtZ/a/rfVg14/hakZJm/D1dkuydPOv+TOLUOI B92Ic31/AjvRxxuhaSgSyNi3FtuvOiZlV9CE0p5hcs43LQ9p6mjkMMBjGvnmhUsuFQuD IYUg== MIME-Version: 1.0 X-Received: by 10.60.198.228 with SMTP id jf4mr879743oec.32.1423137375700; Thu, 05 Feb 2015 03:56:15 -0800 (PST) In-Reply-To: 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>

<20150203112631 DOT 3507a0c1 AT Parasomnia DOT thuis DOT lan> <20150204054256 DOT Horde DOT Pm1JV8RJbICk9SHvIGwZ7A3 AT webmail DOT in-berlin DOT de> <20150204073758 DOT Horde DOT czAmF2JsXvWH254t3K1lrw2 AT webmail DOT in-berlin DOT de> <201502041241 DOT t14Cfd30005029 AT envy DOT delorie DOT com> Date: Thu, 5 Feb 2015 12:56:15 +0100 Message-ID: Subject: Re: [geda-user] FOSDEM From: Svenn Are Bjerkem To: geda-user Content-Type: multipart/alternative; boundary=001a113472b2bece40050e55fd3d 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 --001a113472b2bece40050e55fd3d Content-Type: text/plain; charset=UTF-8 On 5 February 2015 at 11:20, wrote: > However, I think the more abstract concept of footprints being > parameterized - so that, for instance, you can define how you want DIPs to > look and have them all be consistent with each other without defining and > maintaining 8-pin, 14-pin, 16-pin, and 40-pin DIPs separately by hand - is > important and valuable. It seems a shame that gEDA once had that ability > and now basically doesn't. > Back in the days when I worked with Cadence Composer, I used to have fun with pcells in schematic capture: The switches I used in spice simulations were parametrized to be closed when they were closed and open when they were open in simulation. Other things we used parametrized schematics for were transistors. We could have had a separate symbol for all possible types of transistors and just change W and L, but the EDA team created a pcell which changed its looks depending on the parameters we set in the transistor properties. Cadence used a Lisp dialect (SKILL) to do the dynamic things. I don't know if this is still the case, but point was that it was the same language as their framework language, so I could write small Lisp snips to iterate over the entities in my schematic and do stuff from their command line. The last command reference I used had a bit more than 5000 commands spread over schematics, simulation, netlisting, layout etc. I had my share of SKILL snippets to do frequently done jobs quick, and knowing SKILL was a skill worth keeping people employed to know. SKILL knowledge can be used for most other Lisp languages. I don't know where M4 knowledge will take me, so it scares me off.... -- Svenn --001a113472b2bece40050e55fd3d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On 5= February 2015 at 11:20, <mskala AT ansuz DOT sooke DOT bc DOT ca> = wrote:

However, I think the more abstract concept of footpr= ints being
parameterized - so that, for instance, you can define how you want DIPs to<= br> look and have them all be consistent with each other without defining and maintaining 8-pin, 14-pin, 16-pin, and 40-pin DIPs separately by hand - is<= br> important and valuable.=C2=A0 It seems a shame that gEDA once had that abil= ity
and now basically doesn't.

Back in the days when I worked with Cadence Co= mposer, I used to have fun with pcells in schematic capture: The switches I= used in spice simulations were parametrized to be closed when they were cl= osed and open when they were open in simulation. Other things we used param= etrized schematics for were transistors. We could have had a separate symbo= l for all possible types of transistors and just change W and L, but the ED= A team created a pcell which changed its looks depending on the parameters = we set in the transistor properties.

Cadence used a Lisp dialect (SKILL) to do the dynamic things. I don'= t know if this is still the case, but point was that it was the same langua= ge as their framework language, so I could write small Lisp snips to iterat= e over the entities in my schematic and do stuff from their command line. T= he last command reference I used had a bit more than 5000 commands spread o= ver schematics, simulation, netlisting, layout etc. I had my share of SKILL= snippets to do frequently done jobs quick, and knowing SKILL was a skill w= orth keeping people employed to know.

SKILL knowledge can be used for most other Lisp languages. I don't k= now where M4 knowledge will take me, so it scares me off....

--

Svenn

--001a113472b2bece40050e55fd3d--