From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: What happened to (defun x)? Date: Sat, 24 Nov 2007 15:06:26 -0800 Message-ID: <200711242306.lAON6Qod008147@oogie-boogie.ics.uci.edu> References: <87k5o9h25c.fsf@everybody.org> <200711242144.lAOLi93Q006275@oogie-boogie.ics.uci.edu> <85bq9juwuf.fsf_-_@lola.goethe.zz> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1195945744 7312 80.91.229.12 (24 Nov 2007 23:09:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 24 Nov 2007 23:09:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Nov 25 00:09:11 2007 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.50) id 1Iw47X-0005N1-NL for ged-emacs-devel@m.gmane.org; Sun, 25 Nov 2007 00:09:08 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iw47J-0007Eh-4P for ged-emacs-devel@m.gmane.org; Sat, 24 Nov 2007 18:08:53 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Iw47G-0007DO-7o for emacs-devel@gnu.org; Sat, 24 Nov 2007 18:08:50 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Iw47E-0007B4-MP for emacs-devel@gnu.org; Sat, 24 Nov 2007 18:08:49 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Iw47E-0007Ax-Iv for emacs-devel@gnu.org; Sat, 24 Nov 2007 18:08:48 -0500 Original-Received: from oogie-boogie.ics.uci.edu ([128.195.1.41]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Iw479-0000rZ-Vz; Sat, 24 Nov 2007 18:08:44 -0500 Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by oogie-boogie.ics.uci.edu (8.13.6/8.13.6) with ESMTP id lAON6Qod008147; Sat, 24 Nov 2007 15:06:26 -0800 (PST) In-Reply-To: <85bq9juwuf.fsf_-_@lola.goethe.zz> (David Kastrup's message of "Sat, 24 Nov 2007 23:01:28 +0100") Original-Lines: 33 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 9 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:84085 Archived-At: David Kastrup writes: > Dan Nicolaescu writes: > > > mah@everybody.org (Mark A. Hershberger) writes: > > > > > I have just merged a minimally tested nXML. I merged all the > > > char-name/unicode/*.el files for now because, while this information is > > > in the unicode branch, it isn't in HEAD. That still needs to be sorted > > > out. > > > > Could you please fix the byte compile warnings? We are trying to > > eliminate all the byte compiler warnings. > > The free variable and defsubst warnings have been fixed in the rest of > > emacs code. > > Also it looks like all the the char-name/unicode/*.el files need a > > (declare-function nxml-define-char-name-set at the start. > > I might have missed the discussion: pre-22 we had considered having > (defun nxml-define-char-name-set) > be a byte-compiler silencer in the same manner as > (defvar preview-version) > is a byte-compiler silencer. The obvious advantage over > "declare-function" is that one does not need to remember another idiom > and name. > > Is there a particular advantage for a separate declare-function that I > just am not able to see? `declare-function' was the result of a long, long discussion on this list. Please read that discussion and the reasons this design was chosen before restarting the same discussion again. At least restart the discussion from an informed position.