delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2016/02/16/15:32:33

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Tue, 16 Feb 2016 15:32:21 -0500
Message-Id: <201602162032.u1GKWL7Y005291@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to:
<CAC4O8c9jr_b376SpuUk5HrJApP1c75oxsEBemn-i_xtC-rt-Zw 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> <CAC4O8c9jr_b376SpuUk5HrJApP1c75oxsEBemn-i_xtC-rt-Zw AT mail DOT gmail DOT com>
Reply-To: geda-user AT delorie DOT com

> The excuse is that doing that will lead to bugs.

The context was "what should gnetlist allow?"  The answer is:
everything it can.  If the downstream tools have limits, let them
manage those limits themselves.  Why should gnetlist, or even a
netlist backend, limit what *it* can handle, if it doesn't have to?

If I change the pcbfwd netlister to fail on '$' for some then-valid
reason in pcb, and pcb itself changes to allow '$', I have to go back
and "fix" the netlister (and possibly older but previously installed
netlisters) to allow it.  There's no reason for that.  If the user
puts it in the schematic, and the netlister *can* pass it downstream,
it *should*.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019