Mail Archives: geda-user/2015/10/21/18:50:16
--Apple-Mail=_EB260982-3FB4-4AF2-99E6-A38B175E5328
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
On Oct 21, 2015, at 12:41 PM, Evan Foss (evanfoss AT gmail DOT com) [via =
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> The only changes that can not be undone are too user expectations.
> We need a regression testing suite for the gnetlist backends.
There=E2=80=99s the beginning of such a thing at =
geda-gaf/gnetlist/tests/. Netlister regression checking is tricky, =
though, as there=E2=80=99s much ambiguity. There are generally many ways =
to write equivalent netlists. A back end designed specifically for =
regression testing of the gnetlist API could be a good thing.
> What
> also needs to happen is added documentation of all the workflows we
> support so that a list of what a user/developer can expect is made.
What about future workflows?
>=20
> * Every list of connected pins can have a netname but it is not =
required.
> * A list of connections can only have one netname.
This one is hard to check, because a checking script only sees one name =
for the net, regardless.
> * Using the same netname twice with out showing a visual connection
> still creates a valid connection.
> * Every pin has to have a pinnumber.
Those are implicit in the design, hard to change, I think, so yes.
> * Pins may not have duplicate numbers.
More precisely, netlisting is troublesome unless there is at most one =
instance of a given (refdes pinnumber) pair in the design. However, if =
the back end asks the right question, it can see the duplicates and =
determine how they connect. This might be useful for interchangeable =
pins.
We have tools for checking =E2=80=9Crules=E2=80=9D, but they work =
relative to their designers=E2=80=99 models of the flow. We have seen =
that these do not apply to every flow. And every once in while some =
crazy person wants something completely unanticipated by the developers =
(like a graphical Makefile generator ;-). It=E2=80=99s thus the gnetlist =
core=E2=80=99s job to present the data to the backend, not to enforce =
rules.
>=20
> I assume there is little if any vagueness left in the backend =
documentation.
You enjoy making jokes, don=E2=80=99t you? =E3=83=84
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_EB260982-3FB4-4AF2-99E6-A38B175E5328
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
iQIcBAEBCgAGBQJWKBaYAAoJEF1Aj/0UKykRx5UP/RihD4Ftqdna2hPF7my+1fZ4
bL5pS278yqOh1IM7UREG9/LDOqrEbdjt+Fczaolz7piIrveDq29CSQzaHt+5epCP
AsgXxJ5dO07LovfOrmVWu+lyIeKTpp7c1UV8JsRtQ5jWRIvknGyHm5fHZeAYOVvm
O2MujQvA0UuSMoSQdRo6MZFRmj0DLMtD7gxwo5wI6MYteVMn+xPm1nXLYRf+LYwc
DY0pFHPz4C/kGm/3/73l5w5too2DkjVsM0rFyeEaklS4VcmxmnZ9DWQ+eh0Ty4lP
nbfdHJDsYw4RXtMbM5CNRBj8NWM3UOPafLqFq67SALFkMcmGxp2JritznsBTFM80
fjrKuFSIQ/JEBsx36GPwOC3OEJMS5IV81KWkq294w8h4g6BgMIZs7TJiswXSsewb
4AZdJnT6sHUWNX+4HipNAO4Bz7WVUHIGd1QO6Ij9OhZtLvCHZC/ISPgApxZn+XSa
1NYyNLUF9KosZY6mmHemblpWZvL8tDk5+E6j5+Dg9nlayhiPbFhUFZf+3nQ605Sj
kRrpuHq9rKddz4BdHeN2eIG419BnfGnP5wJdAxDD5ThA+4bHO+bod5Z/n9vy16SQ
xnc0rAg+44epgwH0yURdge1X1j886veU7SDAUee3uKzyVx7dYdqJPZ/QJwiuswmM
Rt31Z/5rjNiT6zD+svQu
=8NXH
-----END PGP SIGNATURE-----
--Apple-Mail=_EB260982-3FB4-4AF2-99E6-A38B175E5328--
- Raw text -