From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: =?utf-8?Q?Jostein=20Kj=C3=B8nigsen?= Newsgroups: gmane.emacs.devel Subject: Re: Include modern-cpp-font-lock into GNU Emacs Date: Mon, 20 Aug 2018 11:28:42 +0200 Message-ID: <1534757322.75605.1479728696.2BF2BB66@webmail.messagingengine.com> References: <53cad8eb-9bf1-e2d3-90cf-10a9874bf69b@lud.cc> <20180811145124.GA4992@ACM> <4e10dfa3-4793-f680-8a85-78a489884cad@lud.cc> <866005o2ko.fsf@gmail.com> Reply-To: jostein@kjonigsen.net NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_----------=_1534757323756050" Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1534757247 3819 195.159.176.226 (20 Aug 2018 09:27:27 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 20 Aug 2018 09:27:27 +0000 (UTC) Cc: Alan Mackenzie To: Andy Moreton , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 20 11:27:22 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 1frgT3-0000t6-Fa for ged-emacs-devel@m.gmane.org; Mon, 20 Aug 2018 11:27:22 +0200 Original-Received: from localhost ([::1]:45715 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1frgV9-0000jw-UU for ged-emacs-devel@m.gmane.org; Mon, 20 Aug 2018 05:29:31 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45345) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1frgUT-0000jr-5x for emacs-devel@gnu.org; Mon, 20 Aug 2018 05:28:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1frgUO-0007VW-Jq for emacs-devel@gnu.org; Mon, 20 Aug 2018 05:28:49 -0400 Original-Received: from out1-smtp.messagingengine.com ([66.111.4.25]:57395) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1frgUO-0007VO-Ar for emacs-devel@gnu.org; Mon, 20 Aug 2018 05:28:44 -0400 Original-Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id B71742188C; Mon, 20 Aug 2018 05:28:43 -0400 (EDT) Original-Received: from web5 ([10.202.2.215]) by compute6.internal (MEProxy); Mon, 20 Aug 2018 05:28:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= secure.kjonigsen.net; h=cc:content-transfer-encoding :content-type:date:from:in-reply-to:message-id:mime-version :references:reply-to:subject:to:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=/GkHoIwnIe8LQrz1XBmLVj2E+L8vVKK1XPIvF4jdG +g=; b=eGXUcIfxavlye2kVF+U3W8PbgbTdrQoVqAbwiULSA4RhjHJCKNKhVXtsA rhIT2+zrsN5nB4iIVxYEM7QhRRpuNGMMdOraJpEE0Iz+y+3HOApPR83ptGe/E8r3 Gse1mAqrGHV+vv09O0LZbyVJId3MqC4SNSmDJb5wpCwF7PcIti3Hr+2iV0TlE8n7 yazkeGhN+IlMWbmKZD8Vi0WVVg/rUctu+KB3DsPPKGQBOrwxKBFwxX61i9lMRuaY ItbHczxjWjMMk18a+xd0MX+b9CLiOU/PFmqszIXvZStgBvrVCTFYVTJSjdgoA7Bj yCWgS7+6xHbyq0W4YyW6ILWNV3xBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :reply-to:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=/GkHoIwnIe8LQrz1XBmLVj2E+L8vVKK1XPIvF4jdG+g=; b=DGyHVtzg1c1X v+amWEvRrDFcmjtnRCXgv95ngyLyXz5wLrn0fyyvz9i7aZFGXdhVWRdpf8LcylwI Az+iZExUisjHKos2YEvxf1z4YFlTMFg1vbHQ/dCnOlOzMmtR3cZJ6ISnCFi5lIde s4JIB+rQKg56VMPPEh/QRkumb5ANP/Cb2dmKTcuVmVzFGWEx4QBc5jRrs3Gewpdx ayhqPStm34MWircspftiGiDguN3bohd+plQNaVAHQwoqDmpNgHlIls5ULvSt3wwU 9AnmnxStSqwyXN5vj/TwW3a9H1CLx+Qgv46VYUClnN1SwINmZ5ofoGx/jaAGdrJC gIv0NQVo1A== X-ME-Proxy: X-ME-Sender: Original-Received: by mailuser.nyi.internal (Postfix, from userid 99) id 1A3ED9E1DB; Mon, 20 Aug 2018 05:28:43 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface - ajax-7b72137a In-Reply-To: <866005o2ko.fsf@gmail.com> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 66.111.4.25 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:228717 Archived-At: This is a multi-part message in MIME format. --_----------=_1534757323756050 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" On Mon, Aug 20, 2018, at 10:38 AM, Andy Moreton wrote: > On Sun 19 Aug 2018, Richard Stallman wrote: >=20 >> [[[ To any NSA and FBI agents reading my email: please >> consider ]]]>> [[[ whether defending the US Constitution against all = enemies, >> ]]]>> [[[ foreign or domestic, requires you to follow Snowden's >> example. ]]]>>=20 >> > So, distributing CC-mode as a GNU ELPA package (like we already >> > do for>> > python.el, org-mode, and a few other bundled packages) would >> > solve this>> > problem, right? >>=20 >> The Emacs release needs to include CC-mode. >=20 > Releasing an ELPA package in addition to the built-in version allows > users an easy way to upgrade their emacs installation to use a newer > version of CC mode without having to wait for the next emacs release.>=20 > AndyM >=20 >=20 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. With such a decoupling, this will no longer be possible, and we should find a new way to give third-party major-modes dependant on cc-mode to ensure compatibility. Maybe cc-mode should ship with its own programmatically accessible version- number to check against? -- Regards Jostein Kj=C3=B8nigsen jostein@kjonigsen.net =F0=9F=8D=B5 jostein@gmail.com https://jostein.kjonigsen.net --_----------=_1534757323756050 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

On Mon, Aug 20, 2018, at 10:38 AM, Andy Moreton wrote:
On Sun 19 Aug 2018, Richard Stallman wrote:<= br>

[[[ To any NSA and FBI agents reading my email: please con= sider    ]]]
[[[ whether defending the US Constitution against all enemies,   =   ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]=

> So, distributing CC-mode as a GNU ELPA package (like we already d= o for
> python.el, org-mode, and a few other bundled packages) would solv= e this
> problem, right?

The Emacs release needs to include CC-mode.

Releasing an ELPA package in addition to the built-in version allows
users an easy way to upgrade their emacs installation to use a newer
version of CC mode without having to wait for the next emacs release.<= br>

    AndyM



As I've mentioned in another reply on this subject, decoupling cc= -mode releases from Emacs-releases will make it harder for third-party majo= r-modes deriving from cc-mode to maintain compatibility when cc-mode introd= uces breaking changes.

Currently we can inspect "cc-mode version" by checking emacs-version, = and dispatching compatible code based on that.

With such a decoupling, this will no longer be possible, and we should= find a new way to give third-party major-modes dependant on cc-mode to ens= ure compatibility.

Maybe cc-mode should ship with its own programmatically accessible ver= sion-number to check against?

--
Regard= s
Jostein Kj=C3=B8nigsen

jostein@k= jonigsen.net =F0=9F=8D=B5 jostein@= gmail.com
https://= jostein.kjonigsen.net



--_----------=_1534757323756050--