X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=YQW5DoSlyRFAOMCn46OUsXvyXWXXfPnf0YLRvK6fins=;
	b=NvZjbHWmkjgT3IWiFSA/HNh2jIQhJpbCVYWeNw3rWPIiV6wuF7wy5f7dRN7TYsI/K/
	xNIXDarmfBqtQFtEz4WUHJLGM+9xbmBl17g5Xg3CpknFr/VLHoN/DujkuODWoSqzfQW9
	xFpQ0idU0jL4OUpWeiQ9qcuTTqo/PKpP3CTcmbKzjnTQLom54+y6vXco689sqTQsBtSj
	21UQdMaUDjBbZoVe+6ZS7lejOv5HtQCMSpDyuDNKo/Szuu/cW5P0XcjkE0JuG1bRo+2k
	eRY9NxBvciiMAok2JTlnb3RsYFPy3380/clarAWtp9e15NmTunHJIpEcQfSSV/bixIrT
	/FuQ==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type;
	bh=YQW5DoSlyRFAOMCn46OUsXvyXWXXfPnf0YLRvK6fins=;
	b=hvDSONbxGpWSfknTjELpnYB0pwLfbDqKkz5om6Zr6ybTFWiXvFBri31igaexH8H+3I
	n3l2tcKu0p+y2Noidkk7XMzRMTxsDD2ztWnq46GtupJx+besynvHzWn55PnbwIp/JweZ
	tTkjcf1Aj6ekr9uyb8kEPPatTue0B2WIyX4LtkJCmts5p8TALWih4KS0n9BYhDjcz1jl
	1x7s4ca38rCS/W4ox8WnACFDmrl6Gg50321+z7BQY8+LxgwB5rzc2U7nOGlrT81BZveR
	YgIg39Haxmy8AlQrutlrbwHESdHCflSduixm5Sw/UwNL7T1kbAHWJ9jJyK198Z6Vw1Ju
	0dxg==
X-Gm-Message-State:	AG10YORM7Sjl7u/3V2G/avDjIjvfl8HOeP9MEJM2E8sAGWavP3275GOMDPkO1q6hTzW+mh4bt8rNxNX07imo1g==
MIME-Version:	1.0
X-Received:	by 10.194.71.70 with SMTP id s6mr9102362wju.1.1455825570746; Thu,
	18 Feb 2016 11:59:30 -0800 (PST)
In-Reply-To:	<201602162032.u1GKWL7Y005291@envy.delorie.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>
	<D3167F4D-4750-49F8-9125-BDC4937F5C69 AT noqsi 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>
	<CAJXU7q_w5NunkojiCr36RHRTq0hJ+PZP1e0GumTRMoGXcvgRXQ AT mail DOT gmail DOT com>
	<201602161715 DOT u1GHFMBB028078 AT envy DOT delorie DOT com>
	<CAC4O8c9jr_b376SpuUk5HrJApP1c75oxsEBemn-i_xtC-rt-Zw AT mail DOT gmail DOT com>
	<201602162032 DOT u1GKWL7Y005291 AT envy DOT delorie DOT com>
Date:	Thu, 18 Feb 2016 10:59:30 -0900
Message-ID:	<CAC4O8c-ig=0UVAqagNXH_DBmC9uVQDu3Y1Gx7LBGmRCo0-_kVQ@mail.gmail.com>
Subject:	Re: [geda-user] pcb import schematic crash, parantheses in netname
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
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

On Tue, Feb 16, 2016 at 11:32 AM, DJ Delorie <dj AT delorie DOT com> wrote:
>
>> The excuse is that doing that will lead to bugs.
>
> The context was "what should gnetlist allow?"  The answer is:
> everything it can.  If the downstream tools have limits, let them

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.

> manage those limits themselves.  Why should gnetlist, or even a
> netlist backend, limit what *it* can handle, if it doesn't have to?

Because you *know* it's gonna break downstream stuff, and fixing bugs
is generally cheaper the closer you detect them to where they occur.
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.

> 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

So what?  In the meantime you haven't confused the heck out of users
for no real gain.

> 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*.

I disagree, for the reasons above.

Britton

- Raw text -