unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joe Corneli <jcorneli@math.utexas.edu>
Subject: Re: Error: Symbol's value as variable is void
Date: Fri, 25 Mar 2005 20:48:26 -0600	[thread overview]
Message-ID: <E1DF1Le-0002Do-00@lab45.ma.utexas.edu> (raw)
In-Reply-To: <7ewtrvff90.fsf@ada2.unipv.it> (message from Thien-Thi Nguyen on Sat, 26 Mar 2005 01:00:11 +0100)



   > when is it good to use `eval-when-compile'?

   when you want to evaluate something at compilation time.

   if this is not completely clear to you, probably it is
   best to drop its use and come back to it later (if ever).

I'm OK with that, but still, I've seen it used, for example, in the
definition of `lisp-imenu-generic-expression'.  It might be helpful to
me to know why it is used there.  I guess otherwise the regexp-opt
forms would not be evaluated when the code was compiled, leading to
disaster.  And I also suppose that this situation is precipitated by
the use of `purecopy'.  So what are the benefits of `purecopy'?
One thing that is kind of quirky is that 
 
 (describe-variable 'lisp-font-lock-keywords-1)

produces a window headed off by "lisp-font-lock-keywords-1's value is
shown below."  No source file.  Wow, weird.

Anyway, I think I was mislead in thinking that it was the things
(potentially) inside of `eval-when-compile' that would precipitate
needing to use it.  Apparently that is not the case.

So, its all becoming much clearer.

  reply	other threads:[~2005-03-26  2:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.227.1111777231.28103.help-gnu-emacs@gnu.org>
2005-03-26  0:00 ` Error: Symbol's value as variable is void Thien-Thi Nguyen
2005-03-26  2:48   ` Joe Corneli [this message]
     [not found]   ` <mailman.255.1111806378.28103.help-gnu-emacs@gnu.org>
2005-03-27  0:12     ` Stefan Monnier
2005-03-27  0:45       ` Joe Corneli
2005-03-28 20:18 ` Kevin Rodgers
2005-03-25 18:28 Joe Corneli
2005-03-25 19:26 ` Denis Bueno

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=E1DF1Le-0002Do-00@lab45.ma.utexas.edu \
    --to=jcorneli@math.utexas.edu \
    /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.
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).