From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: CL function's docstrings Date: Fri, 20 May 2005 01:57:28 +0200 Message-ID: References: Reply-To: Juanma Barranquero NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1116547038 6519 80.91.229.2 (19 May 2005 23:57:18 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 19 May 2005 23:57:18 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 20 01:57:17 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DYusr-0007nv-IW for ged-emacs-devel@m.gmane.org; Fri, 20 May 2005 01:56:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DYuva-0000X2-Sg for ged-emacs-devel@m.gmane.org; Thu, 19 May 2005 19:59:47 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DYuvG-0000P8-Eo for emacs-devel@gnu.org; Thu, 19 May 2005 19:59:26 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DYuvC-0000Lu-4I for emacs-devel@gnu.org; Thu, 19 May 2005 19:59:22 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DYuvB-0000LT-VO for emacs-devel@gnu.org; Thu, 19 May 2005 19:59:22 -0400 Original-Received: from [64.233.184.202] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DYv1h-0007ox-0n for emacs-devel@gnu.org; Thu, 19 May 2005 20:06:05 -0400 Original-Received: by wproxy.gmail.com with SMTP id 50so945668wri for ; Thu, 19 May 2005 16:57:28 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qfgAXyAeMhmmtT8WIUk7RBeCsvSxT0yPhIAHUp16SZpd6Hn2B9A5xL0629eYQ2lsm+ziPL6Vjk5TOZ8g2MgUkLnQ47LTFJZYXtvkijOtWD7T9umgyrgZ68E+YbFAB8sePzgLipOEX4eHnk3RP2jW/GUG84cWp6fu41oXZ6BSWAM= Original-Received: by 10.54.50.46 with SMTP id x46mr1386415wrx; Thu, 19 May 2005 16:57:28 -0700 (PDT) Original-Received: by 10.54.82.6 with HTTP; Thu, 19 May 2005 16:57:28 -0700 (PDT) Original-To: emacs-devel@gnu.org In-Reply-To: Content-Disposition: inline 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:37373 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:37373 > However, coherence between functions is one factor in what > makes any particular argument name better or worse. Sure, of course. That's why I said "absolute". Anyway, as I share Kim's (and others') worries about even small changes during a freeze (other than cosmetic, like docstring fixes, obsolescence declarations, substituting an aliased function with the original, etc.), I think the best plan is: - Use "\(fn ARG1 ARG2...)" now (so 22.1 at least has good cl docstrings) - Use the best method available, once we branch 22.1 That represents doing twice the fixing, but I don't mind, and it'll get us the best results (assuming I don't screw up the docstrings :) --=20 /L/e/k/t/u