unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Subject: Re: New function `emacs-version>='
Date: Fri, 02 May 2003 23:00:47 +0200	[thread overview]
Message-ID: <20030502224227.C2FC.LEKTU@terra.es> (raw)
In-Reply-To: <67B8CED503F3D511BB9F0008C75DAD66054855C9@dewdfx17>

On Fri, 2 May 2003 21:55:31 +0200 , "Wedler, Christoph" <christoph.wedler@sap.com> wrote:

> Specific features or bug fixes are only available in newer Emacsen and
> packages must be able to cope with it.

I used to think like you, and even had such a function in my .emacs (to
cope with 20.7, 21.[123], 21.2.9[0-5], EMACS_21_1_RC and HEAD).

Now I don't. You say:

> The right test is
> 
>  - I need to check the availibility for feature/fix A
>  - feature/fix A is provided with Emacs-X.Y
>  - therefore I test with (emacs-version>= X Y)

but the right test is:

 - I want to use feature/fix A
 - therefore, I test whether A is available.

Whether the feature is available in version X.Y is not that clear-cut,
specially if you're testing for a feature that appears in a branch
before being installed in the trunk (or even as a temporary measure,
while another, better fix is installed on the trunk). Checking for a
particular release is pointless, because you're not really interested in
the release, you're interested in the feature.

What's wrong with using fboundp, boundp, facep? There are 23/11/6 of
them (respectively) in my .emacs and it works really fine...

                                                           /L/e/k/t/u

  reply	other threads:[~2003-05-02 21:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02 19:55 [Suggestion] New function `emacs-version>=' Wedler, Christoph
2003-05-02 21:00 ` Juanma Barranquero [this message]
2003-05-02 21:14   ` Stefan Monnier
2003-05-02 21:35     ` Juanma Barranquero
2003-05-03 11:12       ` Ehud Karni
2003-05-03 13:54         ` Juanma Barranquero
2003-05-03 16:08           ` Stephen J. Turnbull
2003-05-04 19:15             ` Juanma Barranquero
2003-05-06 11:05               ` Stephen J. Turnbull
2003-05-04 13:04           ` Richard Stallman
2003-05-03 17:48     ` Reiner Steib
2003-05-03 18:42       ` Stefan Monnier
2003-05-05 13:47         ` sort-coding-systems in 21.3 and RC branch (was: New function `emacs-version>=') Reiner Steib
2003-05-06  7:08           ` Kenichi Handa
2003-05-02 21:16 ` [Suggestion] New function `emacs-version>=' Thien-Thi Nguyen
2003-05-04 13:03 ` Richard Stallman
2003-05-05 12:52   ` Wedler, Christoph
2003-05-05 13:20     ` Juanma Barranquero
2003-05-05 19:11     ` Richard Stallman
2003-05-05 21:59     ` Luc Teirlinck
2003-05-06 23:42 ` Istvan Marko

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=20030502224227.C2FC.LEKTU@terra.es \
    --to=lektu@terra.es \
    /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).