From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Andy Moreton Newsgroups: gmane.emacs.devel Subject: Re: Include modern-cpp-font-lock into GNU Emacs Date: Mon, 20 Aug 2018 12:28:07 +0100 Message-ID: References: <53cad8eb-9bf1-e2d3-90cf-10a9874bf69b@lud.cc> <20180811145124.GA4992@ACM> <4e10dfa3-4793-f680-8a85-78a489884cad@lud.cc> <866005o2ko.fsf@gmail.com> <1534757322.75605.1479728696.2BF2BB66@webmail.messagingengine.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1534765109 15199 195.159.176.226 (20 Aug 2018 11:38:29 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 20 Aug 2018 11:38:29 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.50 (windows-nt) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 20 13:38:24 2018 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 1friVr-0003qC-Pi for ged-emacs-devel@m.gmane.org; Mon, 20 Aug 2018 13:38:23 +0200 Original-Received: from localhost ([::1]:46332 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1friXy-0004Rb-9Q for ged-emacs-devel@m.gmane.org; Mon, 20 Aug 2018 07:40:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55130) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1friWp-0004IE-Ds for emacs-devel@gnu.org; Mon, 20 Aug 2018 07:39:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1friM4-0001AW-3P for emacs-devel@gnu.org; Mon, 20 Aug 2018 07:28:19 -0400 Original-Received: from [195.159.176.226] (port=49629 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1friM3-00019Y-SZ for emacs-devel@gnu.org; Mon, 20 Aug 2018 07:28:16 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1friJu-0005TX-TW for emacs-devel@gnu.org; Mon, 20 Aug 2018 13:26:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 16 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:3kUejVaPGqsR5FzwX8FeYyjUixY= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 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:228719 Archived-At: On Mon 20 Aug 2018, Jostein Kjønigsen wrote: > As I've mentioned in another reply on this subject, decoupling cc-mode > releases from Emacs-releases will make it harder for third-party major- > modes deriving from cc-mode to maintain compatibility when cc-mode > introduces breaking changes. > Currently we can inspect "cc-mode version" by checking emacs-version, > and dispatching compatible code based on that. Checking version numbers is the wrong approach for feature detection, and should only be a last resort if checking behaviour is not practical. If an ELPA package results in more frequent updates to cc-mode then third party extension authors will simply have to adapt to a slightly faster release cadence. AndyM