Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Emacs version compatibility
Date: Thu, 02 Feb 2012 13:26:12 +0100	[thread overview]
Message-ID: <87bophmnff.fsf@gmx.de> (raw)
In-Reply-To: <87boph33v2.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 02 Feb 2012 11:51:29 +0100")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> But I was thinking that (as with gnulib), projects would just copy stuff
> from the compat library at will as they need it, instead of having to
> include the entire shebang.  And they'd include different bits of it,
> according to what Emacs versions they attempt supporting.

Sure. First step into this direction could be a modularization of that
compat library into compat22.el, compat23.el, xcompat.el.

compat22.el would include compatibility functions needed in Emacs 22 and
introduced in Emacs 23, and compat23.el would include those from Emacs
24 aso. In Gnus, you could do

(if (featurep 'xemacs)
    (require 'xcompat)
  (require 'compat23))

In Tramp, I would also require compat22.el (as long as I'm not bored of
Emacs 22 support).

And there is a relation between fsf-compat.el from XEmacs, and
xcompat.el.

Best regards, Michael.



  reply	other threads:[~2012-02-02 12:26 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 [this message]
2012-02-02 12:32           ` Lars Ingebrigtsen
2012-02-02 13:02             ` Michael Albinus
2012-02-02 13:28               ` Lars Ingebrigtsen
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=87bophmnff.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=ding@gnus.org \
    --cc=larsi@gnus.org \
    /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).