From: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
To: Andy Moreton <andrewjmoreton@gmail.com>, emacs-devel@gnu.org
Subject: Re: Include modern-cpp-font-lock into GNU Emacs
Date: Mon, 20 Aug 2018 19:54:16 +0200 [thread overview]
Message-ID: <1534787656.2221947.1480287024.78B80C56@webmail.messagingengine.com> (raw)
In-Reply-To: <vz1tvnpb7lk.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
On Mon, Aug 20, 2018, at 1:28 PM, Andy Moreton wrote:
> 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
>
Agreed, but (to my knowledge) Emacs lacks proper introspection
capacities, and there's no way up front to know if a function requires
3 or 5 parameters until you've called it and your code has crashed.
Compared to that, verifying version numbers against known points of
change seem like a much better strategy. It is also the advice I've
received from other people around in the Emacs-community.
--
Regards
Jostein Kjønigsen
jostein@kjonigsen.net 🍵 jostein@gmail.com
https://jostein.kjonigsen.net
[-- Attachment #2: Type: text/html, Size: 2372 bytes --]
next prev parent reply other threads:[~2018-08-20 17:54 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
2018-08-20 11:28 ` Andy Moreton
2018-08-20 17:54 ` Jostein Kjønigsen [this message]
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=1534787656.2221947.1480287024.78B80C56@webmail.messagingengine.com \
--to=jostein@secure.kjonigsen.net \
--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.