From: Noam Postavsky <npostavs@gmail.com>
To: "Jostein Kjønigsen" <jostein@kjonigsen.net>
Cc: Alan Mackenzie <acm@muc.de>,
Andy Moreton <andrewjmoreton@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Include modern-cpp-font-lock into GNU Emacs
Date: Mon, 20 Aug 2018 06:51:29 -0400 [thread overview]
Message-ID: <CAM-tV-8j4tcxBMx0V8Xg9AHcJ9k-omxC1-CBi1x_Fm7HSAgW_A@mail.gmail.com> (raw)
In-Reply-To: <1534757322.75605.1479728696.2BF2BB66@webmail.messagingengine.com>
On 20 August 2018 at 05:28, Jostein Kjønigsen
<jostein@secure.kjonigsen.net> wrote:
> 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?
I think this already exists:
c-version is a variable defined in ‘cc-defs.el’.
Its value is "5.33.1"
This variable may be risky if used as a file-local variable.
Documentation:
CC Mode version number.
next prev parent reply other threads:[~2018-08-20 10:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 20:24 Include modern-cpp-font-lock into GNU Emacs Ludwig PACIFICI
2018-08-11 14:51 ` Alan Mackenzie
2018-08-12 0:22 ` Stefan Monnier
2018-08-19 11:16 ` Ludwig PACIFICI
2018-08-19 12:31 ` Stefan Monnier
2018-08-20 3:03 ` Richard Stallman
2018-08-20 8:38 ` Andy Moreton
2018-08-20 9:28 ` Jostein Kjønigsen
2018-08-20 10:51 ` Noam Postavsky [this message]
2018-08-20 11:28 ` Andy Moreton
2018-08-20 17:54 ` Jostein Kjønigsen
2018-08-20 19:45 ` Michael Albinus
2018-08-22 12:46 ` Noam Postavsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM-tV-8j4tcxBMx0V8Xg9AHcJ9k-omxC1-CBi1x_Fm7HSAgW_A@mail.gmail.com \
--to=npostavs@gmail.com \
--cc=acm@muc.de \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jostein@kjonigsen.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.