unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bob Rogers <rogers-emacs@rgrjr.dyndns.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: eval-when-compile vs defconst
Date: Sat, 11 Nov 2006 12:01:14 -0500	[thread overview]
Message-ID: <17750.474.277857.851065@rgrjr.dyndns.org> (raw)
In-Reply-To: <ulkmi6o9n.fsf@member.fsf.org>

   From: Stephen Leake <stephen_leake@member.fsf.org>
   Date: Sat, 11 Nov 2006 09:39:32 -0500

   I ran across this construct in ada-mode.el:

   (eval-when-compile
     (defconst ada-95-string-keywords
       '("abstract" "aliased" "protected" "requeue" "tagged" "until")
       "List of keywords new in Ada 95.
   Used to define `ada-*-keywords'."))

   Is there any point to the 'eval-when-compile'? Help for
   eval-when-compile says;

       Like `progn', but evaluates the body at compile time if you're
       compiling. Thus, the result of the body appears to the compiler as
       a quoted constant. In interpreted code, this is entirely
       equivalent to `progn'.

   Since the body is already a quoted constant, this seems redundant. I
   suspect the eval-when-compile is left over from a previous version
   when functions where used to build the string.

It says "the _result_ of the body", i.e. after compile-time evaluation.

					-- Bob Rogers
					   http://rgrjr.dyndns.org/

  reply	other threads:[~2006-11-11 17:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 14:39 eval-when-compile vs defconst Stephen Leake
2006-11-11 17:01 ` Bob Rogers [this message]
2006-11-11 17:03   ` Bob Rogers
2006-11-12  5:14 ` Richard Stallman
2006-11-12 14:29   ` Stephen Leake
2006-11-12 19:06     ` Markus Triska
2006-11-13  9:43     ` Richard Stallman
2006-11-13 18:41       ` Stuart D. Herring
2006-11-13 18:46         ` Markus Triska
2006-11-13 20:18         ` Stefan Monnier
2006-11-14 12:27         ` Richard Stallman

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=17750.474.277857.851065@rgrjr.dyndns.org \
    --to=rogers-emacs@rgrjr.dyndns.org \
    --cc=emacs-devel@gnu.org \
    /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).