X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
From:	geda AT psjt DOT org (Stephan =?utf-8?Q?B=C3=B6ttcher?=)
To:	"Nicklas Karlsson \(nicklas.karlsson17\@gmail.com\) \[via geda-user\@delorie.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>
	<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>
	<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>
Date:	Mon, 22 Feb 2016 08:56:37 +0100
In-Reply-To:	<20160222074947.0f31d0ee70fbc56e2b4123ad@gmail.com> (Nicklas
	Karlsson's message of "Mon, 22 Feb 2016 07:49:47 +0100")
Message-ID:	<s6noab941qi.fsf@blaulicht.dmz.brux>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id u1M7usGs013762
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

"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via
geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> writes:

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

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.  

There must not be seqfaults.

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.

-- 
Stephan

- Raw text -