X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
Date:	Tue, 16 Feb 2016 13:14:04 -0500
Message-Id:	<201602161814.u1GIE4N8030809@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	geda-user AT delorie DOT com
In-reply-to:
	<CAJXU7q9d9VqBmqabKfE3M3banZ8jn2c3LaWxBSK9_YCm9XN3_w AT mail DOT gmail DOT com>
	(geda-user AT delorie DOT com)
Subject:	Re: [geda-user] pcb import schematic crash, parantheses in netname
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> <CAJXU7q9d9VqBmqabKfE3M3banZ8jn2c3LaWxBSK9_YCm9XN3_w AT mail DOT gmail DOT com>
Reply-To:	geda-user AT delorie DOT com

> On the other hand, we already use "/" for discerning hierarchy, so that
> already implies a certain restriction of legal characters within a net-name
> portion. I'm sure we may also run into problems with our existing format,
> with "-", where "-" is present in the net-name, and/or pin-name. (U1-1,
> U2-2 etc..)

You're talking about "what are legal characters for refdes's and
netnames" but I'm talking about "what characters should gnetlist be
able to handle properly".  At the level of "what strings get passed
through without gnetlist crashing" it should be UTF-8.

Sure there are syntax-related characters like / and - but those aren't
problems *for gnetlist* as long as it passes them downstream
correctly.

If we decide we want to allow characters like / and - in netnames,
refdes's, and whatnot, then we need to come up with a way for those
names to be communicated between gschem and downstream without
corruption or confusion - assuming downstream has a way of doing so.
gsch2pcb uses '-' between refdes and pin, but File->Import doesn't,
for example, so if we want to allow '-' in a netname, either gsch2pcb
needs to be prepared to see two '-'s or we have to deprecate it in
favor of File->Import.

- Raw text -