X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 X-Authenticated-UID: jpd AT noqsi DOT com Content-Type: multipart/signed; boundary="Apple-Mail=_3F5E7A30-3727-4588-9EB3-809434A37A82"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] pcb import schematic crash, parantheses in netname X-Pgp-Agent: GPGMail 2.5.2 From: John Doty In-Reply-To: <201602162032.u1GKWL7Y005291@envy.delorie.com> Date: Tue, 16 Feb 2016 13:47:37 -0700 Message-Id: <4F334436-95D2-472E-A7FA-B51E2A884B12@noqsi.com> References: <20160215215221 DOT fd472794e7b9446a243bfc40 AT gmail DOT com> <201602152055 DOT u1FKtM4K011038 AT envy DOT delorie DOT com> <20160215220938 DOT bbc7eaa59d827cd0b261ea97 AT gmail DOT com> <201602152135 DOT u1FLZrw9012774 AT envy DOT delorie DOT com> <7F210DE7-0A0B-42F9-ABBE-2C2768621186 AT noqsi DOT com> <20160216081722 DOT 1065cbed6653d3da4ffc7498 AT gmail DOT com> <201602160724 DOT u1G7Ox26001785 AT envy DOT delorie DOT com> <20160216085628 DOT b70143c330cd4da98a4603d3 AT gmail DOT com> <201602160805 DOT u1G85d8c003148 AT envy DOT delorie DOT com> <20160216092912 DOT 7f7439f703b49175a21dbb1b AT gmail DOT com> <201602161715 DOT u1GHFMBB028078 AT envy DOT delorie DOT com> <201602162032 DOT u1GKWL7Y005291 AT envy DOT delorie DOT com> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) 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 --Apple-Mail=_3F5E7A30-3727-4588-9EB3-809434A37A82 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 On Feb 16, 2016, at 1:32 PM, DJ Delorie wrote: >=20 >> The excuse is that doing that will lead to bugs. >=20 > The context was "what should gnetlist allow?" The answer is: > everything it can. If the downstream tools have limits, let them > manage those limits themselves. Why should gnetlist, or even a > netlist backend, limit what *it* can handle, if it doesn't have to? +1 >=20 > If I change the pcbfwd netlister to fail on '$' for some then-valid > reason in pcb, and pcb itself changes to allow '$', I have to go back > and "fix" the netlister (and possibly older but previously installed > netlisters) to allow it. There's no reason for that. If the user > puts it in the schematic, and the netlister *can* pass it downstream, > it *should*. >=20 I can imagine that those who can read the characters might prefer the = netname =E2=80=9C=E9=AB=98=E5=9C=A7=E2=80=9D to =E2=80=9CHV=E2=80=9D or = =E2=80=9CHighVoltage=E2=80=9D. When you=E2=80=99re trying to pack = information into small spaces, Roman letters sometimes seem clumsy. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail=_3F5E7A30-3727-4588-9EB3-809434A37A82 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 iQIcBAEBCgAGBQJWw4rqAAoJEF1Aj/0UKykRP9AP/R3a8Z/J2sApxhGMQKHIOGqo 4mAxtw6kqxDsuOspMBDTwT+m8/StxYGza5QUnRK9T687fNd6OvTQQ2a6deBiYo8M SDy/Zs/ojqGTjpb/Hvdqe7QFDFf2m0OT1FTiZ7qKtm0+GeduEBrIqDQeLdJIzkng tCquWfHo80WrK9Fj+fsNGrDjO2BNS8L3HLoWPm7RUYbQW+f6t5mPsQ8bb3L0eOfk /1bCj5Ys/D9g3A4IXezBIdBSSnuVUWFktounjfqcFelDUiMmMR0Ntuury6LI0wK7 WlVIAOzRykcD13gd//5oFvN7ZCRANuTqrDzJ7a9vHiwXaGBZ0VeIDZXOMcx5svD8 k0spnY6lN92Usld1m0+YSJ9oHVQSbfJkZFnWUF+v54BOt2jKWV2RxUPYWaaj/vBO 40cHXB+xGNLw5fRsh9OPZJxaUGgJ8/3boelLH7VNY2SyPuJbIGyJvcKnRkgWeRfT xGh+f5XwWL7KSaL9UDajjb0wyvZOWWwhZFz4z0gxaJqwA6QlYIQpL4MG9E0jcDJk iCkgJKXHoF0rCeBVwm2nYc950FIvumPNTrOOpn/LEZfCXOgFEawVwt+IcVz38gsp kH9Eyjd+GvO+MU0mgvL87cr8GRM1wQWeQ+kp7X2CWOkLpw2Ts0aMswlskdHK4O2r kbObq6VVgUyRuBikeGl6 =Z9cO -----END PGP SIGNATURE----- --Apple-Mail=_3F5E7A30-3727-4588-9EB3-809434A37A82--