Mail Archives: geda-user/2016/02/18/16:06:42
--Apple-Mail=_5A107120-B3ED-4AA2-8A22-1243F02D64E2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
On Feb 18, 2016, at 12:59 PM, Britton Kerin (britton DOT kerin AT gmail DOT com) =
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
> On Tue, Feb 16, 2016 at 11:32 AM, DJ Delorie <dj AT delorie DOT com> 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
>=20
> I disagree. It doesn't add much to accept weird characters. UTF-8 is
> full of chars that *look* identical but compare non-equal, its nuts to
> send them to anything except a human reader if you can avoid it.
It=92s a UTF-8 world, we should be part of it. But you can=92t even =
avoid the problem in ASCII. 0 and O. Or 1, I, l, and |.
>=20
>> manage those limits themselves. Why should gnetlist, or even a
>> netlist backend, limit what *it* can handle, if it doesn't have to?
>=20
> Because you *know* it's gonna break downstream stuff,
But you don=92t know which characters break which downstream stuff. =
Should gnetlist restrict netnames to upper case for SPICE?
> and fixing bugs
> is generally cheaper the closer you detect them to where they occur.
You don=92t even know where the netlist is coming from. It=92s the =
downstream processing=92s job to avoid breakage. If the downstream has =
problems that can=92t be fixed, and the netlister is gnetlist, it may be =
useful to dodge them in the back end. Gnetlist has the machinery to =
support this.
> And that's the case here: the user doesn't know wtf is going on and
> that the problem is really upstream of gnetlist. It would be better
> to set up gnetlist st by default it pukes on weird stuff that's going
> to confuse downstream stuff. If user's want kanji let them set an
> option to get it.
I completely disagree. The toolkit=92s job is to enable the user to do =
what they need, not to get in their way.
>=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
>=20
> So what? In the meantime you haven't confused the heck out of users
> for no real gain.
You don=92t know what other users need, so you can=92t say =93no real =
gain=94. No real gain for you, maybe.
>=20
>> 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 disagree, for the reasons above.
>=20
> Britton
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_5A107120-B3ED-4AA2-8A22-1243F02D64E2
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
iQIcBAEBCgAGBQJWxjJOAAoJEF1Aj/0UKykRa2YP/0Dfr8YY4k+McWvCk0EtkNZk
XUBwMZs4/8nOV2IZdWXrAkqihhtDHq8Zw+z01mnv6WkoW8XU/rU6fFH6kpOmNxj5
5h3lsYvu59Xr8txvjbo4nCdzgoX841yxhgPPUTVsQTBawXWs3J7Jae1fzD9SAhed
3U03C/Yc+ewRgSZ3HfE7XKlzrSyO+XqT42qYHSZgZCTibKXY5G/4gy53FZfe/nQC
Xg0XmxkJZw/V1PqDiYAD7jkOT//la8Havv37Wrf9mUGKf5IOwvFiJtdclDOKjPlw
D3Vn1d0iW3G2mgQQlY2AlxqTy8yf0o7JdYu9HIjNg11OOKzaPVLKC2wo7mLH5c2H
+86H3hzFUV7Pc6sB1IFsJ7r7lpA1ji7DqAD6Jq38AkzDD9ZmlN3/RZy2+buAZc5a
k3SmcDg4jWDtbYjycCxha2rl4LNVkmzWQGTohkkdP8Gnw7Vuk3T/TFIjnkbEUCgS
fE9C+9abM7GAP/E+jcHbQQJQlEHbl5GLuuO/yktzwz64whFIsIGca7DW6spNBC2H
r++KWPNvOHKXcdVJ0ZYXOgrJgTH1ID9et1U8Ua2scMXoEYfKwgJDzW8L+yc5wtOy
eb2038Bn1PNschXE1Y0audufCYa1B4e+PLUdwec7ZETlQCNa8yDvirXsg8o2stv4
Kj1QBh80I5IBhneGen0I
=EQbP
-----END PGP SIGNATURE-----
--Apple-Mail=_5A107120-B3ED-4AA2-8A22-1243F02D64E2--
- Raw text -