From: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
To: emacs-devel@gnu.org
Cc: Alan Mackenzie <acm@muc.de>
Subject: cc-mode: Make all parameters introduced in Emacs 26 optional
Date: Mon, 22 Jan 2018 09:09:21 +0100 [thread overview]
Message-ID: <1516608561.1943450.1243462056.1A47A60F@webmail.messagingengine.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
Hey everyone.
While cc-mode seems to be a foundation for lots of the major-modes
shipped with Emacs, it's also used by third-party packages.
For major-modes shipped with Emacs, changes to the core cc-mode
functions is not that big of a problem, since they can be changed in
tandem with the changes to cc-mode itself.
For third party modules (like csharp-mode, which I maintain), changes to
cc-mode core-functions are more problematic due to Emacs lacking
reliable introspection capabilities.
As an example in the Emacs 26 branch c-font-lock-declarators is now
declared like this:
(defun c-font-lock-declarators (limit list types not-top &optional template-
class) ...)
While in Emacs 25.3 and earlier it's declared like this:
(defun c-font-lock-declarators (limit list types)
...)
Basically the number of mandatory parameters has been bumped from 3 to
4, with another optional parameter added.
These kinds of changes makes it harder for third party modules to
maintain compatibility across Emacs-versions.
Wouldn't it be better to make *all *the new parameters optional and thus
maintain compatibility? Are there any good reasons not to do so?
--
Regards
Jostein Kjønigsen
jostein@kjonigsen.net 🍵 jostein@gmail.com
https://jostein.kjonigsen.net
[-- Attachment #2: Type: text/html, Size: 2291 bytes --]
next reply other threads:[~2018-01-22 8:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 8:09 Jostein Kjønigsen [this message]
2018-01-22 20:32 ` cc-mode: Make all parameters introduced in Emacs 26 optional Alan Mackenzie
2018-02-03 5:59 ` Matthew Carter
2018-02-03 6:13 ` Matthew Carter
2018-02-03 11:44 ` Alan Mackenzie
2019-03-30 13:51 ` Alan Mackenzie
2019-03-30 16:39 ` Stefan Monnier
2019-03-30 19:42 ` Alan Mackenzie
2019-03-30 20:17 ` Stefan Monnier
2019-03-30 21:53 ` Ergus
2018-03-12 20:16 ` Jostein Kjønigsen
2018-03-12 22:40 ` Stefan Monnier
2018-03-12 23:29 ` Clément Pit-Claudel
2018-03-13 1:00 ` Stefan Monnier
2018-03-13 20:08 ` Jostein Kjønigsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1516608561.1943450.1243462056.1A47A60F@webmail.messagingengine.com \
--to=jostein@secure.kjonigsen.net \
--cc=acm@muc.de \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).