From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: ding@gnus.org
Subject: Re: Emacs version compatibility
Date: Thu, 02 Feb 2012 14:28:20 +0100 [thread overview]
Message-ID: <87liol4b63.fsf@gnus.org> (raw)
In-Reply-To: <8739atl776.fsf@gmx.de> (Michael Albinus's message of "Thu, 02 Feb 2012 14:02:05 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
> You might support Emacs 22, and you might need this compatibility
> code. Then you decide to drop Emacs 22 support, and you might not need
> it any longer. How would you know whether you still need this code?
> And how would you organize to take only the compatibility functions
> for Emacs 23 and up?
Well, if you say "./configure --with-emacs=emacs23; make" and you then
get a warning about function `foo' being undefined or taking the wrong
number of parameters, then you just copy that function from the compat
library, and you're done.
Removing stuff you no longer need is slightly trickier, but isn't really
that vital, either. If there are a few functions your targets no longer
need, that's no catastrophe.
But if you want to remove stuff, the just remove the entire compat file
and see what warnings you get, and put the stuff you need back in.
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Rome
next prev parent reply other threads:[~2012-02-02 13:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 13:15 Lars Ingebrigtsen
2012-02-01 13:37 ` Steinar Bang
2012-02-01 18:07 ` Ted Zlatanov
2012-02-01 19:40 ` Lars Ingebrigtsen
2012-02-02 7:40 ` Reiner Steib
2012-02-02 8:51 ` Michael Albinus
2012-02-02 8:59 ` David Engster
2012-02-02 9:47 ` Lars Ingebrigtsen
2012-02-02 10:43 ` Michael Albinus
2012-02-02 10:51 ` Lars Ingebrigtsen
2012-02-02 12:26 ` Michael Albinus
2012-02-02 12:32 ` Lars Ingebrigtsen
2012-02-02 13:02 ` Michael Albinus
2012-02-02 13:28 ` Lars Ingebrigtsen [this message]
2012-02-02 13:39 ` Michael Albinus
2012-02-02 13:03 ` Ted Zlatanov
2012-02-02 13:29 ` Lars Ingebrigtsen
2012-02-02 13:57 ` Ted Zlatanov
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=87liol4b63.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=michael.albinus@gmx.de \
/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.
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 NNTP newsgroup(s).