From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Paul Wallington Newsgroups: gmane.emacs.devel Subject: Re: Some vc-dispatcher nitpicks Date: Sat, 17 May 2008 11:42:28 +0100 Message-ID: References: <20080516195554.GA23205@thyrsus.com> <3D93D0E7-511D-4D93-81DC-4CD3B5658395@pobox.com> <20080516220831.GC23205@thyrsus.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (Apple Message framework v919.2) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1211020984 32218 80.91.229.12 (17 May 2008 10:43:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 17 May 2008 10:43:04 +0000 (UTC) Cc: Glenn Morris , emacs-devel@gnu.org, esr@snark.thyrsus.com To: esr@thyrsus.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat May 17 12:43:41 2008 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 1JxJt3-0000UR-LW for ged-emacs-devel@m.gmane.org; Sat, 17 May 2008 12:43:37 +0200 Original-Received: from localhost ([127.0.0.1]:41066 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JxJsK-00023J-1K for ged-emacs-devel@m.gmane.org; Sat, 17 May 2008 06:42:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JxJsF-00022K-J5 for emacs-devel@gnu.org; Sat, 17 May 2008 06:42:47 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JxJsE-00020I-66 for emacs-devel@gnu.org; Sat, 17 May 2008 06:42:47 -0400 Original-Received: from [199.232.76.173] (port=57579 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JxJsD-00020B-UV for emacs-devel@gnu.org; Sat, 17 May 2008 06:42:45 -0400 Original-Received: from a-sasl-fastnet.sasl.smtp.pobox.com ([207.106.133.19]:61481 helo=sasl.smtp.pobox.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JxJsA-0001OH-65; Sat, 17 May 2008 06:42:42 -0400 Original-Received: from localhost.localdomain (localhost [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 6441C2E05; Sat, 17 May 2008 06:42:41 -0400 (EDT) Original-Received: from mini.home (host86-146-4-91.range86-146.btcentralplus.com [86.146.4.91]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 5F4612E04; Sat, 17 May 2008 06:42:36 -0400 (EDT) In-Reply-To: <20080516220831.GC23205@thyrsus.com> X-Mailer: Apple Mail (2.919.2) X-Pobox-Relay-ID: F9B3915C-23FD-11DD-ACA3-80001473D85F-02562057!a-sasl-fastnet.pobox.com X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) 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:97315 Archived-At: On 16 May 2008, at 23:08, Eric S. Raymond wrote: > John Paul Wallington : >> `gensym' is a function rather than a macro and it apparently doesn't >> have a corresponding compiler macro. Use or loading of cl at >> runtime by >> packages that are installed in the Emacs sources is verboten. > > Hmmm...can anyone explain why that is? It should be docunted > somewhere. It's policy. It is documented in the elisp manual; see (elisp) Coding Conventions: * Please don't require the `cl' package of Common Lisp extensions at run time. Use of this package is optional, and it is not part of the standard Emacs namespace. If your package loads `cl' at run time, that could cause name clashes for users who don't use that package. However, there is no problem with using the `cl' package at compile time, with `(eval-when-compile (require 'cl))'. That's sufficient for using the macros in the `cl' package, because the compiler expands them before generating the byte-code. >> Is it okay to install the following patch? > > Yes, that looks good. Thanks. It might be possible to remove the > eval-compile > of cl, as well, once you've done this; you'd be doing me a favor if > you checked. Checked it. Doesn't work, though I mistakenly thought it did. O_o