From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: Re: master 1e3b0f2: Improve doc strings of project.el Date: Mon, 13 Jul 2020 09:58:42 +0200 Message-ID: <20200713075842.GA4332@tuxteam.de> References: <294212ed-5a6e-0a7f-e1c2-97e917f1e6e1@yandex.ru> <83eepgomts.fsf@gnu.org> <83a704okmg.fsf@gnu.org> <5d59dd9b-0848-691a-615e-c16d2070b92d@yandex.ru> <837dv8oida.fsf@gnu.org> <834kqcoghk.fsf@gnu.org> <99bb8976-580a-ef8e-6b7d-130c3ca5cb8a@yandex.ru> <83y2nom3hy.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3278"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/1.5.21 (2010-09-15) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jul 13 09:59:30 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jutN4-0000mb-Bx for ged-emacs-devel@m.gmane-mx.org; Mon, 13 Jul 2020 09:59:30 +0200 Original-Received: from localhost ([::1]:38116 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jutN3-0002Yu-Ew for ged-emacs-devel@m.gmane-mx.org; Mon, 13 Jul 2020 03:59:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37554) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jutMS-0001xs-9v for emacs-devel@gnu.org; Mon, 13 Jul 2020 03:58:52 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]:54553) by eggs.gnu.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.90_1) (envelope-from ) id 1jutMQ-0002qv-63 for emacs-devel@gnu.org; Mon, 13 Jul 2020 03:58:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:To:Date; bh=t1edtGLoeVG3OFq+ubA0MKWJyLYkrkPgCKk5QsIEuT0=; b=TfZV24ACkNZhNjccdmrEgz/kZ/ezmTVyZuGSe0KC/bbIsibzorOn1KnZiouowC/lOzcOiNzq9BNSL3altpnUtsJHW53Cj66QYKv3U0tE8vxs2q0l3yCON2YsVCbOMEptPAnXUABAaG1R8k3NJUGsg0J3HTR1z7/s9N9gU30/zbaQL4moIWjcyfPEfhr/zKMTjpT/LEZBt54M9CXy0+iNfD+d/PxdpBJzbtn0YDBSHjDDU+Gl+TO0MgoB1pA0gr/KrAS9p7IOIhMjbEuEOBFKP4aHKv1OVWEeCgZZ1PxGp+vqH4NCRgVVD69DCeJpuG2RMcuKE+l8P4yfhP/SNZcL5g==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1jutMI-0001WN-5n for emacs-devel@gnu.org; Mon, 13 Jul 2020 09:58:42 +0200 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de X-detected-operating-system: by eggs.gnu.org: First seen = 2020/07/13 03:58:42 X-ACL-Warn: Detected OS = Linux 3.1-3.10 [fuzzy] X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:252905 Archived-At: --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 13, 2020 at 07:11:21AM +0000, Gregory Heytings via Emacs develo= pment discussions. wrote: [...] > I might be wrong, but I think Dmitry's viewpoint is that if he > documents X, then X becomes part of the API. Other developers will > (or might) use X in their code, and he would not be completely free > to change X anymore [...] Yes. But I think the core of the disagreement lies in *who* decides where the line in the sand is. Dmitry seems to lean to the side "the library designer does", while Eli to the one "it's part of a collective process". I'll leave this at that -- I'm aware that this is a huge issue, and you'll find language designs more slanted to the one or to the other direction, reflecting the one or the other culture. Even the term "API", "application programming interface" conveys the culture on the one side: here be the system programmers (better paid, presumably), there be the application programmers. If one of the latter *dares* to touch system things, (s)he's fired [1]. I wonder where the term "API" originated. I'd guess it comes from the depth of the bowels of a 1960's to 1970's IBM, where you'd have to apply for a variable name to a specialized department [2].=20 Cheers [1] That was a bit tongue-in-cheek, and there *is* IMO a valid case for "separation of concerns", I do it all the time with myself. I just wanted to raise the contrast a bit. [2] Again, lots of tongue-in-cheek and a barrel of salt apply. That thing with a variable name is from memory and might be grossly misremembered. -- t --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAl8MFDIACgkQBcgs9XrR2kbOwQCbBNCSGX2Z/sTDcCkKKptPYR3C 1PAAmwSgc49REJHlp+DxCVi5ale6ujgU =KRbO -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24--