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=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-type:content-transfer-encoding;
	bh=LiCZo/BF01/4FTqoCUn4+xPBHNj4hyP4HjUpbjnspoo=;
	b=Rt6x9Gxnx01MvxmQEclrfs+sXL6gw/Pssfqn7brkEvJZ299Bb4x6Bcv4Ifit9/RZuH
	LLahSziI94BTLOZinuECND4Nvyg9UAakfxNAJW6ZBCRayJqHz7GCr1GJkiMOA14bylT6
	jKGFAiXFwwW9J/Aw/BrmbCEifI1Pkm4Q7PIJVKngHl4xHTKJ6lsbTqnMHxyDaxoyYysI
	PWjUDdnCdabmE1UdpqUaO7aiTi7vnx5awkALXc4PShVMw/PPrKph3TAs/TSH7JuJmkKv
	CnvPRzHDxGseJGegH5hDQAkAEAlkFHpfaC6/MhNs9lwzDSclKgWMCYXUNpZqHfuMoE5+
	qhyg==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	bh=LiCZo/BF01/4FTqoCUn4+xPBHNj4hyP4HjUpbjnspoo=;
	b=W2jokn31aihwHSJXmbW/lmQwnMVUoTKkVeZsatHXxAM3GgXzc5Mp9ZB7IZFW1sGO/i
	F+SajE7FByS9Ws6y5F2nQhQsBSERd61iXpmIw9f3c5KGHL39iAg+RqFNuGMyX7faiBUy
	UoEwOzXkm1GqtCLiv5QXc3qu6lwcfYAWkUaJfZW4wwwglvCVx8EBHeqqgxQG64Oy+2yV
	RpIqXJFrUUnUl/giXCeVkDaQoNF49smIHoga+YZvaYmstUpG9kHdo4YLVgBnc2HT/T4D
	hNVyKg2q1n9QMuw8kd6Nrh3DV2ejxtTCNlytQIdg2908yDWxO3nKlfAi7A28HPNYnvEu
	SEww==
X-Gm-Message-State:	AG10YORufZMvSbEywIp86/DAA7IL5dtat80ZXWZOgAVVPGqgBaOaVVBu0XnZkUSRcze4Uw==
X-Received:	by 10.112.210.165 with SMTP id mv5mr3373143lbc.0.1456131637196;
	Mon, 22 Feb 2016 01:00:37 -0800 (PST)
Date:	Mon, 22 Feb 2016 10:00:32 +0100
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] pcb import schematic crash, parantheses in netname
Message-Id:	<20160222100032.2a617987588f775c0be13741@gmail.com>
In-Reply-To:	<s6noab941qi.fsf@blaulicht.dmz.brux>
References:	<20160215215221 DOT fd472794e7b9446a243bfc40 AT gmail 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>
	<CAC4O8c-ig=0UVAqagNXH_DBmC9uVQDu3Y1Gx7LBGmRCo0-_kVQ AT mail DOT gmail DOT com>
	<E75ECBB6-14E7-437A-B374-E0CF86BDFF1A AT noqsi DOT com>
	<CAC4O8c8z4JiJr=mgA+co4pX-yxu_pVsXpeKRYqneuxZNnYqh8g AT mail DOT gmail DOT com>
	<AB351427-7E08-4412-A796-03E850F2411A AT noqsi DOT com>
	<CAC4O8c8ejSN3GrmB1Zw=Dx9Pm-3Y0jwjNs=yjmwgsqcoVW5ACw AT mail DOT gmail DOT com>
	<20160222074947 DOT 0f31d0ee70fbc56e2b4123ad AT gmail DOT com>
	<s6noab941qi DOT fsf AT blaulicht DOT dmz DOT brux>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version:	1.0
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

> >> >> What to you mean by dodge them in the back end?
> >> >
> >> > There’s code in gnetlist that allows a back end to alias refdes
> >> > and netname values that violate its rules.
> >> 
> >> Rather than rewriting them, it would be better to just trap them and
> >> give a reasonable error message.  This would be less good than a
> >> gschem that catches them immediately, but much better than the current
> >> situation. ...
> >
> > To trap them and give a resonable error message would be the correct
> > path. They could be catched in gschem but it will not work if there
> > are differences between back ends so then running gnetlist would be
> > the correct point.
> 
> The gnetlist backend needs to know the synatx and semantics of the
> output format it produces.  The syntax spec includes quoting needs and
> methods.  It needs to implement them.

Correct.

> The receiver may add additional restrictions to the semantics, if
> needed, like allowed characters in refdes, and throw warnings or error
> messages when those are violated.  It does not make a lot of sense to
> implement the list of disallowed characters twice.

Yes

> There must not be seqfaults.

This is important. As is now there is a seg fault for parantheses then using import schematics in pcb but not then using load schematics.

> It does not make a lot of sense to restrict the allowed char set too
> much. Maybe somebody wants to use verilog to generate a PCB netlist,
> with netnames like \top.core(3,56).x[0] and pin names like \d[4] .
> 
> As for UTF-8, all my resistor values include the unit Ω, and a lot of
> capacitors use µF.

Ωµ are good. Characters from other languages are also good.

> Stephan


Seems like we are on the same track.

Regards Nicklas Karlsson

- Raw text -