Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Emacs version compatibility
Date: Thu, 02 Feb 2012 08:40:06 +0100	[thread overview]
Message-ID: <87k445ptt5.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <871uqey9t4.fsf@gnus.org>

On Wed, Feb 01 2012, Lars Ingebrigtsen wrote:

> I think Ma Gnus should drop Emacs 22 compatibility, and it should also
> drop non-Mule XEmacs compatibility.

Fine with me.  Although dropping Emacs 22 probably doesn't help too
much as long as you support XEmacs 21.4.

> More controversially :-), I think 真 Gnus should also stop defining
> compatibility functions like `gnus-mark-active-p', and instead just
> start maintaining a `gnus-compat.el' library that would define functions
> like `mark-active-p' for Emacsen that don't define them.

Please don't.  It violates the Emacs coding guidelines.  Packages that
have gone that road have broken other packages in the past.
E.g. color-scheme defined `replace-in-string´[1] which broke Gnus and
emacs-jabber.

> This will make the source code more readable, I think.

I can't see that `mark-active-p' is much more readable as
`gnus-mark-active-p´.

Bye, Reiner.

[1]
,----
| From: Reiner Steib
| Subject: Bogus definition of replace-in-string in color-theme.el
|   (was: Fwd: Re: Error viewing PGP/mime signed messages)
| To: Xavier Maillard <xma // gnu.org>
| Cc: Katsumi Yamaoka <yamaoka <at> jpl.org>
| Date: Wed, 19 Mar 2008 13:39:51 +0100
| Message-ID: <v9d4pqj39g.fsf <at> marauder.physik.uni-ulm.de>
| 
| Hi Xavier,
|
| please fix the use of `replace-in-string' in color-theme.el ASAP (see
| the problem described below and in <https://gna.org/bugs/?9494>).
| 
| No package should ever define functions and variables out of it's own
| name space:
| 
| ,----[ (info "(elisp)Coding Conventions") ]
| |    * If a package needs to define an alias or a new function for
| |      compatibility with some other version of Emacs, name it with the
| |      package prefix, not with the raw name with which it occurs in the
| |      other version.  Here is an example from Gnus, which provides many
| |      examples of such compatibility issues.
| | 
| |           (defalias 'gnus-point-at-bol
| |             (if (fboundp 'point-at-bol)
| |                 'point-at-bol
| |               'line-beginning-position))
| `----
| [ Forwarded articles from
|   <http://thread.gmane.org/gmane.emacs.gnus.general/66521/focus=66522>
|   stripped. ]
`----
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  parent reply	other threads:[~2012-02-02  7:40 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 [this message]
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
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=87k445ptt5.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@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).