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=e1yhuxUfT/IN1/b2+Yqau5aoQlcgecAkxt1PikTdZOo=;
        b=SGRayauqrDBfDgJw/9HZD4ZKZZjeYR7wPFMj0fne8FmSSPuOpBwLEeX45jn47pbXMy
         0xNFd6NB49ym01kvQIcw+P5DegNKU90DxjEIGmSvMIpTDeTAoSFFJjsI9gPJ3J04Zxpo
         8k1ZdNkmY9wnR1I4W3Lr3oiyPTb+rMVEscJnnOuXQkZ2R9uR0nSFtIxXsB5ejlDhUHUm
         eZU6Bawz76dtO0kraWscaGOKRdBkWdnk3bDN0pd9zjxlFvm9YwKNVMEhaeFMX0+2u+NB
         7YhE7FuiGyJfUF73FOqfu30etHfHOo5ZhigTKsHs88OwY22m8gCGVKfMLBPARJAAggD0
         BVgQ==
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=e1yhuxUfT/IN1/b2+Yqau5aoQlcgecAkxt1PikTdZOo=;
        b=ZljMYb+qs3UAab8qcDVoHeOLTZRQpHDlSZT3JX3h2Yo5LOfiHfqn2/BYigwguNZiwA
         yp0Vba9F8yTPvBRN4GC8tFUXA+IoFy2FZaQ+y5OlM3091mChwBZazkUmbQhJ75D+IUM6
         9Wh5EG+sTSHesifOm1hqXUTnntsm2ukwOy5skCKp3LtAh4OEaHGvDMNXlNKiUnhvWrZu
         9THs9fMB7vhKgJSXM3vyCT6BgNhtBR5J9dLsG6FVyYZvOsuD8/AxZ1dqEqg5FbHyCsTE
         K9aRIf4CIHFK9gM9lkjg6FBf+qo7WdU27uujNYBqH9D6/VtQofyBi1O5/eXOr2TFKtX4
         kRvA==
X-Gm-Message-State: AG10YOQ3dPc+pvqUCmwV129afXA45qGgXzJ78jO8rXL5G9rBKEfEAgyv4uic9moB/59yog==
X-Received: by 10.112.14.102 with SMTP id o6mr9376549lbc.87.1456123793523;
        Sun, 21 Feb 2016 22:49:53 -0800 (PST)
Date: Mon, 22 Feb 2016 07:49:47 +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: <20160222074947.0f31d0ee70fbc56e2b4123ad@gmail.com>
In-Reply-To: <CAC4O8c8ejSN3GrmB1Zw=Dx9Pm-3Y0jwjNs=yjmwgsqcoVW5ACw@mail.gmail.com>
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>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
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
Precedence: bulk

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

> Britton

Nicklas Karlsson