Mail Archives: geda-user/2015/12/31/20:18:16
--001a1145a83a2bd8e705283b8b55
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Wed, Dec 30, 2015 at 9:44 AM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Dec 30, 2015, at 11:00 AM, karl AT aspodata DOT se wrote:
>
> > Nicklas Karlsson:
> >>> On Dec 20, 2015, at 6:34 AM, karl AT aspodata DOT se wrote:
> >>>
> >>>> I'd like to be able to do, gschem:
> >>>>
> >>>> . give parameters to subsheets, like
> >>>> output is to be 12V select suitable resistor devider
> >>>> this filter has this freq., select suitable components
> >>>
> >>> Neither gschem nor the schematic file format need any
> >>> modification to do this. It works nicely with SPICE. It=E2=80=99s a
> >>> downstream issue.
> >
> > Ok, that is one way to do it. I meant more that I wanted gschem to
> > be able to show alt. the formula or the result, i.e. with the
> > parameter/formula applied.
>
> OK, so go with the logic of the tool and write Scheme scripts to do this.
>
> The idea that something=E2=80=99s wrong with gschem because it doesn=E2=
=80=99t have
> <insert favorite feature> builtin strikes me as an invitation to chaos an=
d
> bloat. It=E2=80=99s like complaining that TeX has no built-in concept of =
what a
> paragraph is.
>
> >
> >>> If you=E2=80=99re doing this for layout in a big project, I think
> >>> you probably want the capability to use automatically generated
> >>> schematic files as your intermediates. The reason is that there=E2=80=
=99s
> >>> a subset of reviewers and technicians who find hierarchy
> >>> challenging, and parameterized hierarchy will be even more
> >>> confusing.
> >
> > Strange, we live in world multiple hierarchies (the company, home,
> > state, etc). Do you have any idea why ?
>
> I think it=E2=80=99s related to a preference for step-by-step thinking. I
> contribute to the Mathematica Stack Exchange group, and the most common
> thing I see that makes code hard to understand and debug is that some
> insist on coding step by step with For[] rather than transforming whole
> structures with Map[], Thread[], etc. The same thing applies to those who
> struggle with Scheme, I think.
>
The JavaScript kids have all met the deferred function call tower of doom
now, so this is unlikely. The more obvious and likely explanation that
they just haven't used the language so it's painful for them in a large
number of small ways, and they don't have any real incentive to work
through them.
Britton
--001a1145a83a2bd8e705283b8b55
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Dec 30, 2015 at 9:44 AM, John Doty <span dir=3D"ltr"><<a hre=
f=3D"mailto:jpd AT noqsi DOT com" target=3D"_blank">jpd AT noqsi DOT com</a>></span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
On Dec 30, 2015, at 11:00 AM, <a href=3D"mailto:karl AT aspodata DOT se">karl AT aspo=
data.se</a> wrote:<br>
<br>
> Nicklas Karlsson:<br>
>>> On Dec 20, 2015, at 6:34 AM, <a href=3D"mailto:karl AT aspodata DOT s=
e">karl AT aspodata DOT se</a> wrote:<br>
>>><br>
>>>> I'd like to be able to do, gschem:<br>
>>>><br>
>>>> . give parameters to subsheets, like<br>
>>>> output is to be 12V select suitable resistor devider<br>
>>>> this filter has this freq., select suitable components<br>
>>><br>
>>> Neither gschem nor the schematic file format need any<br>
>>> modification to do this. It works nicely with SPICE. It=E2=80=
=99s a<br>
>>> downstream issue.<br>
><br>
> Ok, that is one way to do it. I meant more that I wanted gschem to<br>
> be able to show alt. the formula or the result, i.e. with the<br>
> parameter/formula applied.<br>
<br>
</span>OK, so go with the logic of the tool and write Scheme scripts to do =
this.<br>
<br>
The idea that something=E2=80=99s wrong with gschem because it doesn=E2=80=
=99t have <insert favorite feature> builtin strikes me as an invitati=
on to chaos and bloat. It=E2=80=99s like complaining that TeX has no built-=
in concept of what a paragraph is.<br>
<span class=3D""><br>
><br>
>>> If you=E2=80=99re doing this for layout in a big project, I th=
ink<br>
>>> you probably want the capability to use automatically generate=
d<br>
>>> schematic files as your intermediates. The reason is that ther=
e=E2=80=99s<br>
>>> a subset of reviewers and technicians who find hierarchy<br>
>>> challenging, and parameterized hierarchy will be even more<br>
>>> confusing.<br>
><br>
> Strange, we live in world multiple hierarchies (the company, home,<br>
> state, etc). Do you have any idea why ?<br>
<br>
</span>I think it=E2=80=99s related to a preference for step-by-step thinki=
ng. I contribute to the Mathematica Stack Exchange group, and the most comm=
on thing I see that makes code hard to understand and debug is that some in=
sist on coding step by step with For[] rather than transforming whole struc=
tures with Map[], Thread[], etc. The same thing applies to those who strugg=
le with Scheme, I think.<br></blockquote><div><br></div><div style=3D"">The=
JavaScript kids have all met the deferred function call tower of doom now,=
so this is unlikely.=C2=A0 The more obvious and likely explanation that th=
ey just haven't used the language so it's painful for them in a lar=
ge number of small ways, and they don't have any real incentive to work=
through them.</div><div>=C2=A0</div><div style=3D"">Britton</div></div><br=
></div></div>
--001a1145a83a2bd8e705283b8b55--
- Raw text -