Mail Archives: geda-user/2015/02/05/06:57:48
--001a113472b2bece40050e55fd3d
Content-Type: text/plain; charset=UTF-8
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 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
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 5=
February 2015 at 11:20, <span dir=3D"ltr"><<a href=3D"mailto:mskala AT an=
suz.sooke.bc.ca" target=3D"_blank">mskala AT ansuz DOT sooke DOT bc DOT ca</a>></span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div id=3D":6sk" class=3D"a3s" sty=
le=3D"overflow:hidden">However, I think the more abstract concept of footpr=
ints being<br>
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<b=
r>
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<br>
and now basically doesn't.<div class=3D"yj6qo ajU"><div id=3D":6ri" cla=
ss=3D"ajR" tabindex=3D"0"></div></div></div></blockquote></div><br><br></di=
v><div class=3D"gmail_extra">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. <br><br></div><div class=3D"gmail_extr=
a">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.<br><br></div><div class=3D"gmail_extr=
a">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....<br clear=3D"al=
l"></div><div class=3D"gmail_extra"><br>-- <br><div class=3D"gmail_signatur=
e">Svenn</div>
</div></div>
--001a113472b2bece40050e55fd3d--
- Raw text -