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=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=+kSWZXMLTLVUfuUPOUBecjxTUwvQPeyYakhDVxaN4kk=; b=ixjOx0FiwLZ7bW3cQysq+L1rvW78nhKe02lDTFsJ3DOozrWi9eah4NcDC5YEIpdvOR 0tvuDVQLk33GUvpPA0suxGTcAjNuEPb2qaulRRqStDzAZUZW4Xb23mIRhMALXaRdfqXe C68X+Ce0LMqv7cqD9J4z2z8eEzuaxEF6g1qpB2LCtSwUn7txL5Z/wBNEg8JWPj01/3TQ T+vbZKB9yxRjskOqL09zQzAXWEyncr1jaDcUKfFGWINQ0g/k7N5DEnArnM72DVRNmvaL nvZ9Les6vyojHangIWEwA7CUAHFlT+5c/4YOkXCABRq2VN/AG6cLkdowRj7up9Eo6E/X GB1Q== MIME-Version: 1.0 X-Received: by 10.112.198.198 with SMTP id je6mr1798806lbc.31.1444832467856; Wed, 14 Oct 2015 07:21:07 -0700 (PDT) In-Reply-To: References: <1042003D-82E2-40F0-AB60-8186580C46AD AT noqsi DOT com> <201510121905 DOT t9CJ5T9W026297 AT envy DOT delorie DOT com> <88EA58F5-2B23-498A-9E5B-84054976DBED AT noqsi DOT com> <4D3CD563-D8EE-4B2A-975A-AC2B573960FF AT noqsi DOT com> <34B17816-9EA5-45FD-BFB4-9D623A8D3D87 AT noqsi DOT com> <39FF6208-7D45-4DE8-9AEE-1ED1B512705B AT noqsi DOT com> <201510140229 DOT t9E2T45e021346 AT envy DOT delorie DOT com> <38EA4E25-A99C-4732-B803-215D5FCC3264 AT noqsi DOT com> Date: Wed, 14 Oct 2015 10:21:07 -0400 Message-ID: Subject: Re: [geda-user] A lesson from gnet-makefile From: "Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com]" To: gEDA users mailing list Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t9EELCXK015822 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 On Wed, Oct 14, 2015 at 9:32 AM, John Doty wrote: > > On Oct 13, 2015, at 10:20 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: > >> On Wed, Oct 14, 2015 at 4:06 AM, John Doty wrote: >>> >>> On Oct 13, 2015, at 9:46 PM, Evan Foss (evanfoss AT gmail DOT com) [via geda-user AT delorie DOT com] wrote: >>> >>>> Yes and I have sided with you on that as I said before often in a >>>> minority of 2 or 3 people. >>>> Ultimately you have to trust people and the community or have your own >>>> fork. Although as the only person who is actively writing gnetlist >>>> backends you basically already have that. >>> >>> But what matters is who’s using them. I have no idea how many, but people do ask questions about them occasionally, so I’m not the only user. >> >> If the users don't use this and it just sits there after a while we >> can redact it. No harm no foul. > > I have schematics that still have promoted attributes that shouldn’t have been promoted due to the change in the default, maybe 5 years ago. That still occasionally creates trouble. > > https://bugs.launchpad.net/geda/+bug/1014160 caused me to release a broken design. I still hate the feature, but nothing will get in the way of developers who prefer clever to simple. > > Subtle problems get released and cause harm before they’re noticed. Definitely foul. That is a change in default and attribute handling. I am just talking about adding a method for reading net attributes. The two are unrelated in all but the most superficial sense. >> >> The closest this comes to having validity is the question will this >> addition break the gnetlist backends we already have. The answer is no >> assuming no one breaks the scheme interface. > > Depends on whether you change the data the scheme interface returns. Do you know all of the implicit assumptions in all of the back ends? Of course, you don’t, nobody does. I don’t think it condescending to assume that you lack clairvoyance. 1. That is only likely to be a problem which will only be an issue if the implementation is sloppy. 2. The backend interface can change (although we should try not to) as long as we make sure all our officially listed backends still work and the change is documented. It should not be that hard to *not* force the new added data on them. Other peoples backends hiding in their own repos are their responsibility. 3. If the new attributes are not compatible with the old netlist backends people should accept that they have a choice between using the new attributes or their prefered older backend. All of which is common sense which we have to assume our fellow contributors have in order to not be condescending. I am not going to entertain this part of the debate any farther. >> >>> John Doty Noqsi Aerospace, Ltd. >>> http://www.noqsi.com/ >>> jpd AT noqsi DOT com >>> >>> >> >> >> >> -- >> Home >> http://evanfoss.googlepages.com/ >> Work >> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >> >> > > John Doty Noqsi Aerospace, Ltd. > http://www.noqsi.com/ > jpd AT noqsi DOT com > > -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/