From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Obtaining a database of new functionality per Emacs version Date: Mon, 07 Dec 2020 20:17:43 +0200 Message-ID: <83a6up8oqg.fsf@gnu.org> References: <83360haauw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30335"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Vasilij Schneidermann Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Dec 07 19:27:28 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 1kmLEN-0007n9-Sm for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Dec 2020 19:27:27 +0100 Original-Received: from localhost ([::1]:39854 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kmLEM-0001EZ-Vg for ged-emacs-devel@m.gmane-mx.org; Mon, 07 Dec 2020 13:27:27 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33880) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kmL59-0003zC-5m for emacs-devel@gnu.org; Mon, 07 Dec 2020 13:17:55 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:32999) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kmL56-0006lm-PQ; Mon, 07 Dec 2020 13:17:53 -0500 Original-Received: from [176.228.60.248] (port=3361 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kmL56-00084V-A2; Mon, 07 Dec 2020 13:17:52 -0500 In-Reply-To: (message from Vasilij Schneidermann on Mon, 7 Dec 2020 18:50:07 +0100) 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:260505 Archived-At: > Date: Mon, 7 Dec 2020 18:50:07 +0100 > From: Vasilij Schneidermann > Cc: emacs-devel@gnu.org > > > Did you try "make TAGS" in the top-level directory, followed by > > searching the TAGS files? > > Thanks, that's the kind of idea I'm looking for. I'd still need to diff > that output against that of an older Emacs version to find out what has > been removed/added between the releases, but that's fine. Another > problem is that it includes helper functions that aren't part of a > public API. I thought the latter problem will not be an issue in your case, since my mental model of what you want was that you have a function in hand and want to check whether it was available in Emacs XX.YY. In which case you will never need to look for internal functions. > > Manually or automatically? If manually, the result will be as > > accurate and comprehensive as NEWS. If automatically, please tell > > what kind of implementation you have in mind. > > Manually, similar to how version information is added to customizables. That needs Someone™ to be extra vigilant and double-check any changes that add functions to prod people to mark them with a version tag. My experience with being that cop in defcustoms case is that the probability of some falling through the cracks is non-negligible. > The gain is having a machine-readable version you can consult from a > Lisp program. Who knows, maybe you could use it to make an Emacs Lisp > spec independent implementations could target... I know of libraries that have this as part of their SOPs, but Emacs is so much larger than any library that I doubt if this scales well enough. So I don't believe such manual procedures will be reliable enough in Emacs. One possible idea is to have a Git commit hook that would reject commits with new functions if they fail to include the necessary tag.