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=googlemail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=q4MIl1huyc7QSM0yf7feXG8pVhJ3xX+Lo1MCSIensMQ=;
	b=XicOAaBUMHqzbngNXhxHVBnyK8Abg4UEM9vx5pKY0PsOyACWA0VASyMQbFCrzzpdu2
	KyMVk3jImRFOhlzBSIKYiCzK7lOR6LX0SYWdAyf76E6rzr4jFzBjsrnqe6Q3buM7Riyl
	9TRGRbNQvPL+8l7paCmcp9UsyyjwHQTKkCI/lHKJkzIlVn8LIwMjOmVBvSI9D+vVeY/l
	ybqXUxuPPWkFo9sfW8tw4X/BkyrciPBVuwH9z4qYrkzt76m9L57ZKRHY6vNySFfXq2v7
	EoeuTwZCbd8ZVm2Plt4zNaz3HHV0pGdvWA8Phej37rNUxjE9iHe99N6ffBXS3cHrqGYk
	1IGw==
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=q4MIl1huyc7QSM0yf7feXG8pVhJ3xX+Lo1MCSIensMQ=;
	b=jd3ZHIVtFlFYwFKe/cbDMjSP4vmgYflqiA1Om8QWmfpxMfCBDRIAoiXh/aIrEJVEy5
	o/yOsTeSj7AsB22f9ZSSf0BreXhGDvzBex21eus60ABgTnGm1v9TwguqJKbiD/2Tycu4
	T5fB+DqPYmlrduiikrPRNL15HuBFwEeSbl4+9gZtH9CPnaLBlCbwPM2FEDXg7r+AHx6+
	sHk3mV6ZkGtF/QJpwF+UCbMPYf3MaMtzJS/asQm8VJLHX1PbiIE9KD0TU+Zrk/qYrf0U
	1RjMmA0pySaVpicznns64R/8TjN4kEf1UZ4SmbuUXfzOdDeN8QJtmgf1LN3M70F4eQtb
	J/ow==
X-Gm-Message-State:	AG10YOSa1XTiH95hqNUOswiXHO4YbmNrfFpHacKZs53GUxnM9xa/Qfc+tMGo6l2wLQh3sCH2B3F0TuE5OmuzDw==
MIME-Version:	1.0
X-Received:	by 10.202.188.134 with SMTP id m128mr18081553oif.4.1455647869282;
	Tue, 16 Feb 2016 10:37:49 -0800 (PST)
In-Reply-To:	<20160216193208.6d801075c1a6af04d408d99a@gmail.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>
	<CAJXU7q9d9VqBmqabKfE3M3banZ8jn2c3LaWxBSK9_YCm9XN3_w AT mail DOT gmail DOT com>
	<0EA9D8BC-9C58-4F34-9130-55A8A52D76D5 AT noqsi DOT com>
	<20160216193208 DOT 6d801075c1a6af04d408d99a AT gmail DOT com>
Date:	Tue, 16 Feb 2016 18:37:49 +0000
Message-ID:	<CAJXU7q-nU3uiOgV_C0rJWnQOynKzyW17Rxx98jbQPLKB7rwd8A@mail.gmail.com>
Subject:	Re: [geda-user] pcb import schematic crash, parantheses in netname
From:	"Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	gEDA User Mailing List <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

--001a113dcc822ad409052be76e93
Content-Type: text/plain; charset=UTF-8

Quite probably..

It isn't really that "official", and it only affects the netlist view.
Since gEDA usually uses "/" as a netlist specifier, that is what I used
when parsing PCB net-names to form a tree.

I'm surprised you're using net-names with "/" in them TBH, but then you
also had brackets - which I would also have considered quite unusual (but
probably fair enough).

Peter

On 16 February 2016 at 18:32, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com)
[via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> > > Ok, that is one approach..
> > >
> > > 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.
>
> Hierachy might explain why I get a foldout then using "/" to separate
> functionality on micro controller pins.
>
>
> Nicklas Karlsson
>

--001a113dcc822ad409052be76e93
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div>Quite probably..<br></div><br></div>It=
 isn&#39;t really that &quot;official&quot;, and it only affects the netlis=
t view. Since gEDA usually uses &quot;/&quot; as a netlist specifier, that =
is what I used when parsing PCB net-names to form a tree.<br><br></div>I&#3=
9;m surprised you&#39;re using net-names with &quot;/&quot; in them TBH, bu=
t then you also had brackets - which I would also have considered quite unu=
sual (but probably fair enough).<br><br></div>Peter<br></div><div class=3D"=
gmail_extra"><br><div class=3D"gmail_quote">On 16 February 2016 at 18:32, N=
icklas Karlsson (<a href=3D"mailto:nicklas DOT karlsson17 AT gmail DOT com">nicklas.ka=
rlsson17 AT gmail DOT com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com">geda-=
user AT delorie DOT com</a>] <span dir=3D"ltr">&lt;<a href=3D"mailto:geda-user AT del=
orie.com" target=3D"_blank">geda-user AT delorie DOT com</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><span class=3D"">&gt; &gt; Ok, that is one a=
pproach..<br>
&gt; &gt;<br>
&gt; &gt; On the other hand, we already use &quot;/&quot; for discerning hi=
erarchy, so that already implies a certain restriction of legal characters =
within a net-name portion.<br>
<br>
</span>Hierachy might explain why I get a foldout then using &quot;/&quot; =
to separate functionality on micro controller pins.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Nicklas Karlsson<br>
</font></span></blockquote></div><br></div>

--001a113dcc822ad409052be76e93--

- Raw text -