From: Matt <matt@excalamus.com>
To: "ihor radchenko" <yantar92@posteo.net>
Cc: "emacs-orgmode" <emacs-orgmode@gnu.org>
Subject: Backwards compatibility (was: Re: [PATCH] ob-shell: consistent prefix)
Date: Sat, 20 Jan 2024 17:03:10 +0100 [thread overview]
Message-ID: <18d279c9696.11f7c699f365957.5930695120108631730@excalamus.com> (raw)
In-Reply-To:
---- On Tue, 16 Jan 2024 14:10:00 +0100 Ihor Radchenko wrote ---
> I do not mind changing the names, except that we must not break
> backwards compatibility. In particular, the non-private function
> and variable names that were present in the latest Org stable
> release must be either supplied with an alias or declared
> obsolete. Otherwise, the third-party code using the old names will
> be broken.
How far does backwards compatibility extend with regard to Org itself? For the next version, for all time, or something else?
The rule I infer from your comment is, "renamed symbols must be aliased." This implies that any arguments associated with the symbol are the same after the name change. How do we handle changes in function APIs? I'm thinking of something like =org-babel-execute:shell= and =org-babel-sh-evaluate= where it would make sense to refactor the =stdin= and =cmdline= parameters.
--
Matt Trzcinski
Emacs Org contributor (ob-shell)
Learn more about Org mode at https://orgmode.org
Support Org development at https://liberapay.com/org-mode
next reply other threads:[~2024-01-20 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-20 16:03 Matt [this message]
2024-01-20 18:54 ` Backwards compatibility (was: Re: [PATCH] ob-shell: consistent prefix) Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18d279c9696.11f7c699f365957.5930695120108631730@excalamus.com \
--to=matt@excalamus.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.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/org-mode.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).