From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: next emacs version? Date: Fri, 19 Mar 2010 23:51:33 -0700 Message-ID: References: <56D10E2523764AC98D99CEBC55DBAD93@us.oracle.com><83iq8sigyq.fsf@gnu.org><83d3z0i3nu.fsf@gnu.org><911BA1D06CEB4306924D0069BA2D3DFF@us.oracle.com><83bpeki18a.fsf@gnu.org><83aau4hv38.fsf@gnu.org><0E10B96B5C814EE8B95B57972F13E189@us.oracle.com> <5E984B3C-4B86-4FA6-8675-4C8501CC2285@raeburn.org> <88C42498-ADC0-45DA-B6AC-698F07AACCA2@raeburn.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1269068052 28000 80.91.229.12 (20 Mar 2010 06:54:12 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sat, 20 Mar 2010 06:54:12 +0000 (UTC) Cc: emacs-devel@gnu.org To: "'Ken Raeburn'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Mar 20 07:54:08 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NssZT-0003YN-Sg for ged-emacs-devel@m.gmane.org; Sat, 20 Mar 2010 07:54:08 +0100 Original-Received: from localhost ([127.0.0.1]:37505 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NssZT-0004IR-Af for ged-emacs-devel@m.gmane.org; Sat, 20 Mar 2010 02:54:07 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NssXg-0003jv-M9 for emacs-devel@gnu.org; Sat, 20 Mar 2010 02:52:16 -0400 Original-Received: from [140.186.70.92] (port=38212 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NssXb-0003gh-Jh for emacs-devel@gnu.org; Sat, 20 Mar 2010 02:52:16 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NssXW-0002tK-HF for emacs-devel@gnu.org; Sat, 20 Mar 2010 02:52:11 -0400 Original-Received: from rcsinet12.oracle.com ([148.87.113.124]:49634) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NssXW-0002tF-93 for emacs-devel@gnu.org; Sat, 20 Mar 2010 02:52:06 -0400 Original-Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet12.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o2K6q2be031459 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 20 Mar 2010 06:52:05 GMT Original-Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o2K6q2tL022870; Sat, 20 Mar 2010 06:52:02 GMT Original-Received: from abhmt003.oracle.com by acsmt353.oracle.com with ESMTP id 97142111269067892; Fri, 19 Mar 2010 23:51:32 -0700 Original-Received: from dradamslap1 (/24.5.179.75) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 19 Mar 2010 23:51:32 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <88C42498-ADC0-45DA-B6AC-698F07AACCA2@raeburn.org> Thread-Index: AcrH7qlMrhXsB7J1TT2Y9qrl+VJqBQABM6Xg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Source-IP: acsmt354.oracle.com [141.146.40.154] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090208.4BA47092.01AB:SCFMA4539814,ss=1,fgs=0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:122348 Archived-At: > > But sometimes (esp. if the release cycle is long) I do make > > changes (esp. if minor) that allow my code to keep working with the latest > > development version. That's sometimes easy when it concerns a > > new var or fn (but not arity change etc. for a fn). > > advice.el has code for figuring out the arg list of a > function, so you can check arity changes. Though, the > easiest way may turn out to be loading advice and calling > ad-arglist.... No, I'm not going to go there. If I really have to deal with that, then I'm more likely to use `condition-case' and try first the newer signature, backing out to the older signature in case of error. (Obviously, that only works for some kinds of changes.)