From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: New function `emacs-version>=' Date: Sat, 03 May 2003 15:54:05 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20030503154455.C412.LEKTU@terra.es> References: <20030502232146.C2FF.LEKTU@terra.es> <200305031112.h43BC9tL013684@beta.mvs.co.il> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1051970330 18731 80.91.224.249 (3 May 2003 13:58:50 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sat, 3 May 2003 13:58:50 +0000 (UTC) Cc: monnier+gnu/emacs@rum.cs.yale.edu Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat May 03 15:58:48 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19BxXM-0004rw-00 for ; Sat, 03 May 2003 15:58:48 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19BxZQ-0000ju-00 for ; Sat, 03 May 2003 16:00:56 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19BxX5-0004TU-07 for emacs-devel@quimby.gnus.org; Sat, 03 May 2003 09:58:31 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 19BxWO-0004AZ-00 for emacs-devel@gnu.org; Sat, 03 May 2003 09:57:48 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 19BxVV-0003Pr-00 for emacs-devel@gnu.org; Sat, 03 May 2003 09:56:54 -0400 Original-Received: from smtp.terra.es ([213.4.129.129] helo=tsmtp7.mail.isp) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 19BxSq-0002YY-00 for emacs-devel@gnu.org; Sat, 03 May 2003 09:54:08 -0400 Original-Received: from [81.40.137.29] ([81.40.137.29]) by tsmtp7.mail.isp (terra.es) with ESMTP id HEBDA400.V2U; Sat, 3 May 2003 15:54:04 +0200 Original-To: ehud@unix.mvs.co.il In-Reply-To: <200305031112.h43BC9tL013684@beta.mvs.co.il> X-Mailer: Becky! ver. 2.05.10 Original-cc: emacs-devel@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:13645 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:13645 On Sat, 3 May 2003 14:12:09 +0300, "Ehud Karni" 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