From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: small elaboration in tips.texi
Date: Mon, 10 Jul 2006 16:29:09 -0600 [thread overview]
Message-ID: <e8ukd2$fqt$1@sea.gmane.org> (raw)
In-Reply-To: <2cd46e7f0607100914x587b58e7g846755525844723c@mail.gmail.com>
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
next prev parent reply other threads:[~2006-07-10 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 16:14 small elaboration in tips.texi Ken Manheimer
2006-07-10 22:29 ` Kevin Rodgers [this message]
2006-07-10 23:05 ` Nick Roberts
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e8ukd2$fqt$1@sea.gmane.org' \
--to=ihs_4664@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).