unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: rgm@gnu.org, emacs-devel@gnu.org, monnier@iro.umontreal.ca, storm@cua.dk
Subject: Re: cl-byte-compile-compiler-macro
Date: Tue, 04 Apr 2006 23:47:30 -0400	[thread overview]
Message-ID: <E1FQyzS-00032Q-Lc@fencepost.gnu.org> (raw)
In-Reply-To: <jemzf1gjrb.fsf@sykes.suse.de> (message from Andreas Schwab on Tue, 04 Apr 2006 22:37:12 +0200)

    > It could be a problem that compiling a call to these macros loads CL.
    > I am not sure; it is on the borderline.
    >
    > Does interpreting a call to these defstruct accessor macros also load CL?

    defstruct is defined in cl-macs, so you can't use it without loading cl.

We are miscommunicating.

We have a file foo.el that uses defstruct and defines an accessor,
foo-bar.  Loading foo.elc will load the compiled definition of
foo-bar.

If another file, quux.el, does (require 'foo), it will load the
compiled definition of foo-bar.  So there are two questions:

When I load quux.el, and run it interpreted, does it need to load
CL in order to process the call to foo-bar?  (Stefan says no.)

When I compile quux.el, does that need CL to be loaded?
(Assume quux.el does not load CL itself.)

  reply	other threads:[~2006-04-05  3:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 21:02 cl-byte-compile-compiler-macro Kim F. Storm
2006-03-23 23:52 ` cl-byte-compile-compiler-macro Glenn Morris
2006-03-24 23:25   ` cl-byte-compile-compiler-macro Richard Stallman
2006-03-25  2:52     ` cl-byte-compile-compiler-macro Glenn Morris
2006-03-25  9:43       ` cl-byte-compile-compiler-macro Glenn Morris
2006-03-25 14:20       ` cl-byte-compile-compiler-macro Andreas Schwab
2006-03-28  6:39         ` cl-byte-compile-compiler-macro Glenn Morris
2006-03-25 15:26       ` cl-byte-compile-compiler-macro Richard Stallman
2006-03-25 20:55         ` cl-byte-compile-compiler-macro Kim F. Storm
2006-03-26 11:21           ` cl-byte-compile-compiler-macro Richard Stallman
2006-03-26 14:10             ` cl-byte-compile-compiler-macro Andreas Schwab
2006-03-27  2:07               ` cl-byte-compile-compiler-macro Stefan Monnier
2006-03-27  9:34                 ` cl-byte-compile-compiler-macro Andreas Schwab
2006-03-27 22:29                 ` cl-byte-compile-compiler-macro Richard Stallman
2006-03-27 23:44                   ` cl-byte-compile-compiler-macro Andreas Schwab
2006-03-28 19:33                     ` cl-byte-compile-compiler-macro Richard Stallman
2006-04-04 19:57                     ` cl-byte-compile-compiler-macro Richard Stallman
2006-04-04 20:37                       ` cl-byte-compile-compiler-macro Andreas Schwab
2006-04-05  3:47                         ` Richard Stallman [this message]
2006-04-05  9:27                           ` cl-byte-compile-compiler-macro Andreas Schwab
2006-04-05 13:04                             ` cl-byte-compile-compiler-macro Stefan Monnier
2006-04-05 19:06                             ` cl-byte-compile-compiler-macro Richard Stallman
2006-04-05 19:32                               ` cl-byte-compile-compiler-macro Stefan Monnier
2006-04-05 19:39                                 ` cl-byte-compile-compiler-macro David Kastrup
2006-04-05 20:12                                   ` cl-byte-compile-compiler-macro Stefan Monnier
2006-04-06  3:58                                 ` cl-byte-compile-compiler-macro Richard Stallman
2006-04-08 15:09                                   ` cl-byte-compile-compiler-macro Stefan Monnier
2006-04-05 21:23                               ` cl-byte-compile-compiler-macro Andreas Schwab
2006-04-04 20:50                       ` cl-byte-compile-compiler-macro Stefan Monnier
2006-03-28  6:52                   ` cl-byte-compile-compiler-macro Glenn Morris

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=E1FQyzS-00032Q-Lc@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rgm@gnu.org \
    --cc=storm@cua.dk \
    /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).