From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: (emacs-version) in the Elisp reference Date: Wed, 21 Jun 2017 05:35:13 +0300 Message-ID: <837f06vzj2.fsf@gnu.org> References: <20EE9F2C-6F30-4A9C-BF0E-E17D4FC7F8FC@gmail.com> <838tkmwude.fsf@gnu.org> <2EF9DD89-50F9-4320-9ED6-999C9D3EE901@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1498012541 1123 195.159.176.226 (21 Jun 2017 02:35:41 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 21 Jun 2017 02:35:41 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 21 04:35:31 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dNVUR-00081y-0F for ged-emacs-devel@m.gmane.org; Wed, 21 Jun 2017 04:35:31 +0200 Original-Received: from localhost ([::1]:51490 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dNVUS-00035R-Ur for ged-emacs-devel@m.gmane.org; Tue, 20 Jun 2017 22:35:32 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59196) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dNVUN-00035M-EA for emacs-devel@gnu.org; Tue, 20 Jun 2017 22:35:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dNVUI-0004d8-HN for emacs-devel@gnu.org; Tue, 20 Jun 2017 22:35:27 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:48817) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dNVUI-0004d4-ET; Tue, 20 Jun 2017 22:35:22 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2837 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dNVUG-0003nM-Qz; Tue, 20 Jun 2017 22:35:22 -0400 In-reply-to: <2EF9DD89-50F9-4320-9ED6-999C9D3EE901@gmail.com> (message from Jean-Christophe Helary on Wed, 21 Jun 2017 08:25:23 +0900) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:215843 Archived-At: > From: Jean-Christophe Helary > Date: Wed, 21 Jun 2017 08:25:23 +0900 > > >> (why hardcode values that do not correspond to the current manual?) > > > > Becuase they are just illustrative examples, and nothing would be gained > > by changing them to always refer to the current version. > > > In that case, I beg to differ. They are in the elisp reference manual to illustrate the values of functions or variables. When you read the manual in the Emacs whose version corresponds to the manual (as it is supposed to be the case) and you evaluate them, there are no reasons why they would not reflect the actual numbers of the Emacs version. This is a very minor issue, to be sure, and so are the gains. We could use the value of EMACSVER where the full version is mentioned. But how do you suggest to change this part: > @defvar emacs-major-version > The major version number of Emacs, as an integer. For Emacs version > 23.1, the value is 23. > @end defvar > > @defvar emacs-minor-version > The minor version number of Emacs, as an integer. For Emacs version > 23.1, the value is 1. > @end defvar to use EMACSVER? Texinfo doesn't have text-processing function to extract the major and minor version numbers from a version string. Are we going to introduce 2 more variables? If so, how will we update them when producing a release? We do that automatically for EMACSVER. Given this complexity, I think you can understand Glenn's response.