From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: John Paul Wallington Newsgroups: gmane.emacs.help Subject: Re: Some racism in emacs! Date: Sun, 01 Jun 2003 08:41:04 +0100 Sender: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <87n0h2jldb.fsf@indigo.shootybangbang.com> References: <87add2tjro.fsf@thalassa.informatimago.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1054453436 19643 80.91.224.249 (1 Jun 2003 07:43:56 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 1 Jun 2003 07:43:56 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Sun Jun 01 09:43:55 2003 Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19MNVT-00056h-00 for ; Sun, 01 Jun 2003 09:43:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19MNWq-0000T8-Ie for gnu-help-gnu-emacs@m.gmane.org; Sun, 01 Jun 2003 03:45:20 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!headwall.stanford.edu!fu-berlin.de!uni-berlin.de!host217-44-221-72.range217-44.btcentralplus.COM!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 40 Original-NNTP-Posting-Host: host217-44-221-72.range217-44.btcentralplus.com (217.44.221.72) Original-X-Trace: fu-berlin.de 1054453489 8442345 217.44.221.72 (16 [170119]) X-Orig-Path: indigo.shootybangbang.com!news X-Attribution: jpw X-Face: R(_z-rF:grdKO.*u`n); p.i$Eiz=h^CO5eDYv"4:K@#\HN09*Ykx}}B{kF/KH}%f_o^Wp List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:10427 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:10427 Pascal Bourguignon wrote: > Well, actually what's bothering me is these nasty, racist messages I > get from the byte-compiler: > > Warning: Function `gensym' from cl package called at runtime > Warning: Function `subseq' from cl package called at runtime > etc... > > > I can't see the difference between the functions defined in > emacs/lisp/emacs-lisp/cl.el and those defined in > emacs/lisp/emacs-lisp/ring.el > Can you? The cl library, like Common Lisp, is big and hard to subset. Amongst the Emacs Lisp Coding Conventions it is suggested: * 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, for the sake of macros. You do that like this: (eval-when-compile (require 'cl)) Hm. I think name clashes are largely a non-problem; a package author would be insane to define cl functions/macros incompatibly, wouldn't they? Ways to ameliorate this situation include splitting cl into several separate independent libraries, moving ultra-nifty bits into subr.el, or defining compiler macros for the more popular functions. If you just don't want to see the warnings then try frobbing `byte-compile-warnings' (untested).