Mail Archives: geda-user/2015/10/14/12:32:23
--Apple-Mail=_94D79124-2F1A-44DE-B962-E1AA9E5C9BCC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
On Oct 13, 2015, at 10:22 PM, Evan Foss (evanfoss AT gmail DOT com) [via =
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> On Wed, Oct 14, 2015 at 4:11 AM, John Doty <jpd AT noqsi DOT com> wrote:
>>=20
>> On Oct 13, 2015, at 9:46 PM, Evan Foss (evanfoss AT gmail DOT com) [via =
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>>=20
>>> True but this is a functionality that should be available everywhere
>>> s_conn is. A point you really have yet to produce a good counter
>>> argument too.
>>=20
>> Maybe you should look at implementing your ideas in the Xorn context. =
No Scheme. This is perhaps the future. Roland certainly seems prolific =
with it: maybe it=92s a quicker way, too.
>=20
> No I want to advance gEDA not the almost totally parallel but
> compatible toolchain Xorn is growing.
Roland and I consider his tool to be part of gEDA. I like the idea of =
having xorn-gnetlist and scheme-gnetlist for the future. Give developers =
a choice of paradigm and language. But to advance scheme-gnetlist, you =
really need to give up your aversion to scheme.
I don=92t get this idea that to advance a toolkit you need to add =
features to the tools. Consider:
Once there was a text editor, QED. QED rewritten for Unix became ed. =
People started using ed in pipelines (clumsy), but instead of adding a =
pipeline =93feature=94, somebody wrote sed. Somebody noticed that g/re/p =
was a common use pattern, and grep was born. None of these things was =
quite what you wanted for complicated data extraction from text files, =
but instead of adding =93features=94 to them, Aho et al. created awk. =
Wall wanted features in place of awk discipline, but wisely created a =
new vehicle for them, perl.
Except for QED, all of these tools remain in common use. The isolation =
of different approaches to the text processing problem in different =
tools is, for many of us, the source of the flexibility of the kit. And =
if you don=92t agree, you can use perl.
>=20
> Like I said eventually we will want to back notation this and that
> means having an understanding of connections in gschem.
I disagree. The tool that feeds the changes into the schematic needs =
such an understanding, but that does not require anything of gschem. For =
one of my projects, I make flattened as-built schematics by annotation =
via lambda-geda. It=92s entirely automated: gschem is not involved.
>=20
>> John Doty Noqsi Aerospace, Ltd.
>> http://www.noqsi.com/
>> jpd AT noqsi DOT com
>>=20
>>=20
>=20
>=20
>=20
> --
> Home
> http://evanfoss.googlepages.com/
> Work
> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/
>=20
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_94D79124-2F1A-44DE-B962-E1AA9E5C9BCC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJWHoOHAAoJEF1Aj/0UKykR768P/RFS5cXZ1aaFPY8Dkq73ujFf
uRQky05196xk2ezUMlWPC/8G0Gjva6zftqQriZMG42Naph9RjkGnsCmA6uKsbjQS
Uy1aegY9NsXXFCJW4eQqsXv18ig1EUZliMaHewwgMzREHI8MWggFs6itbpsWYowL
Izf+QGiSngm26JSIAF60xqLtcLPAJZiq6vkELEtp+UstGmEERVnGK58Q/I5PS5SV
JNxyjzb9TJyWFl7uSmu8ggxhM9J2H5Vx7xYU/tHtyIcSqp7WxWqJ/mPTUAzpWkHv
9h3dCQAkad+SMSDClJw5qmdsRBe1Mk+cRaRozwDIj1DyUhfhBPXOaG9vPiq/74kE
KZYbXVF+qRRCYFrQUt30f/8Njpm4zvksfGbiqWGdalBt/sY3pOrvx7GWDa5R6OI6
m0aOdut4HJfU1/9GPOsHU7W7HY1ZuugUxLyFy+DXUUDHDi10DHqssfv/2LqItyT1
tXkH38mNUIqxj7D+i/jt72hpeFtsw25hMDGWdhTbunXjFutnWRMiUVVuwd+BlJVP
2ctDPhLza0UDczd5oFQIyS22GUgsaE/m/x4kSgZ5FyS6yqakQ3cYOe4s5sWGagbM
+ytHTPKErYzsKz854Fuluh6wn9PIbQsxxBrPYtoYgPhsnqFMxO2ItnTVYzyav7Lc
+9IPV37yrMz+d+4Hadhz
=3I8L
-----END PGP SIGNATURE-----
--Apple-Mail=_94D79124-2F1A-44DE-B962-E1AA9E5C9BCC--
- Raw text -