From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.devel Subject: Re: small elaboration in tips.texi Date: Mon, 10 Jul 2006 16:29:09 -0600 Organization: IHS Message-ID: References: <2cd46e7f0607100914x587b58e7g846755525844723c@mail.gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1152570636 16430 80.91.229.2 (10 Jul 2006 22:30:36 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 10 Jul 2006 22:30:36 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jul 11 00:30:35 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1G04Gs-0007xX-Q0 for ged-emacs-devel@m.gmane.org; Tue, 11 Jul 2006 00:30:31 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G04Gs-0005Bz-5D for ged-emacs-devel@m.gmane.org; Mon, 10 Jul 2006 18:30:30 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G04Gh-0005Bu-PM for emacs-devel@gnu.org; Mon, 10 Jul 2006 18:30:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G04Gg-0005Bi-26 for emacs-devel@gnu.org; Mon, 10 Jul 2006 18:30:18 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G04Gf-0005Bf-VZ for emacs-devel@gnu.org; Mon, 10 Jul 2006 18:30:18 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1G04Hr-0005GN-1a for emacs-devel@gnu.org; Mon, 10 Jul 2006 18:31:31 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1G04GW-0007tc-2V for emacs-devel@gnu.org; Tue, 11 Jul 2006 00:30:08 +0200 Original-Received: from 207.167.42.206 ([207.167.42.206]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 11 Jul 2006 00:30:08 +0200 Original-Received: from ihs_4664 by 207.167.42.206 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 11 Jul 2006 00:30:08 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 29 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 207.167.42.206 User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) In-Reply-To: <2cd46e7f0607100914x587b58e7g846755525844723c@mail.gmail.com> 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:56903 Archived-At: Ken Manheimer wrote: > i hadn't connected the fact that requiring a package for macros can be > limited to the byte-compilation phase, since the macro expansions are > compiled in to the resulting byte-code. i've elaborated the entry > about limiting dependencies on 'cl in tips.texi to convey that fact. > i'm including the patch inline below my signature. ... > --- tips.texi 10 Jul 2006 10:58:03 -0400 1.85 > +++ tips.texi 10 Jul 2006 11:40:42 -0400 > @@ -119,7 +119,9 @@ > that could cause name clashes for users who don't use that package. > > However, there is no problem with using the @code{cl} package at compile > -time, with @code{(eval-when-compile (require 'cl))}. > +time, with @code{(eval-when-compile (require 'cl))}. That's sufficient > +particularly for @code{cl} macros - they are compiled in to the resulting > +byte-code, so @code{cl} becomes unnecessary at run time. > > @item > When defining a major mode, please follow the major mode I would phrase it a little differently: That is sufficient for macros because the compiler expands them before compiling the resulting Lisp forms into byte-code. -- Kevin