unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: New function `emacs-version>='
Date: Sat, 03 May 2003 15:54:05 +0200	[thread overview]
Message-ID: <20030503154455.C412.LEKTU@terra.es> (raw)
In-Reply-To: <200305031112.h43BC9tL013684@beta.mvs.co.il>

On Sat, 3 May 2003 14:12:09 +0300, "Ehud Karni" <ehud@unix.mvs.co.il> wrote:

> > And, as a last resort, you can often do something like
> > 
> >   (unless (ignore-errors XXXX)
> >     YYYY)
> 
> That is NOT always possible

Yeah, well, that's perhaps the reason I wrote "you can *often* do..." :-)

But, honestly, how many cases like this one have you found?

> I have another actual example:
> How do you check that `perform-replace' accept a function in its
> REPLACEMENTS argument (id does in 21.x, does not in 20.x or lower) ?

OK, how do you check that if Emacs does not include emacs-version>= and
will not till 21.4, at the very least? What I mean is that Emacs does
*not* have the function, so you'll be stuck with custom-made checks for
a long time, unless you (as a module author, I mean) are going to drop
support for 21.3- releases. Any answer to the situation is forward
looking, and for that, it's better to be sure any such new change and/or
feature can be properly detected. It's more robust.

OTOH, the use of a function as REPLACEMENTS is not even documented, and
the docstring for `perform-replace' suggests not using the function, so
it's not a very compelling example IMO.

                                                           /L/e/k/t/u

  reply	other threads:[~2003-05-03 13:54 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
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 [this message]
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=20030503154455.C412.LEKTU@terra.es \
    --to=lektu@terra.es \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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).