X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 207.224.51.38 X-Authenticated-UID: jpd AT noqsi DOT com Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: [geda-user] About reinventing the wheel, and how to avoid it From: John Doty In-Reply-To: <201509111941.t8BJfqWl010427@envy.delorie.com> Date: Fri, 11 Sep 2015 13:58:09 -0600 Content-Transfer-Encoding: 7bit Message-Id: References: <201509111624 DOT t8BGOPYV000685 AT envy DOT delorie DOT com> <201509111732 DOT t8BHWnF7005271 AT envy DOT delorie DOT com> <960028A6-F16B-4276-B838-E9F0D2959A6F AT noqsi DOT com> <55F32375 DOT 2020505 AT ecosensory DOT com> <201509111941 DOT t8BJfqWl010427 AT envy DOT delorie DOT com> To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.1878.6) 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 Sep 11, 2015, at 1:41 PM, DJ Delorie wrote: > >> You're saying that when the #1 gEDA developer thinks its a good >> thing to prevent users from using the tools in ways the developers >> don't approve of that I shouldn't worry? > > For the record, I don't think that. > You wrote: > I meant, there may be internal > functions that were never intended to be official (or even public), > that someone discovered and (ab)used in a workflow. There must be a > way to let that API change, despite its use, else we'd be unexpectedly > locked into something we don't want. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com