From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Bug in emacs
Date: Mon, 13 Oct 2003 10:28:06 -0600 [thread overview]
Message-ID: <3F8AD296.7010803@yahoo.com> (raw)
In-Reply-To: mailman.1587.1066050220.21628.bug-gnu-emacs@gnu.org
era@iki.fi wrote:
> If you have macros which influence the meaning of forms you are
> compiling, the macro needs to be loaded before you compile. What you
> are reporting seems like a typical symptom of failing to load the
> macro in question before compiling.
>
> A workaround would be to make sure you eval the macro definition
> before compiling.
>
> I'm not sure what the bug really is. Perhaps it would be useful to get
> a warning when compiling / evaling something when a macro +is+ in
> effect and the file you are compiling is not pulling it in properly?
> Then at least you get a hint to fix it while you still can, while
> those who do it right will not experience any adverse effects.
When the compiler comes across a (function arg ...) form, either the
function is defined or it isn't. If it's defined, either as a function
or a macro, all is well. If it's not defined, the compiler can't know
whether it is a function or a macro and assumes it's a function. A
macro can't be "in effect" if it's file was not loaded "properly".
The compiler does issue warnings when it encounters an undefined
macro/function:
While compiling the end of the data in file /home/kevinr/emacs/foo.el:
** the function bar is not known to be defined.
--
Kevin Rodgers
next prev parent reply other threads:[~2003-10-13 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 13:44 Bug in emacs Jean Pierre Lemue
2003-10-13 12:39 ` era
[not found] ` <mailman.1587.1066050220.21628.bug-gnu-emacs@gnu.org>
2003-10-13 16:28 ` Kevin Rodgers [this message]
2003-10-14 6:05 ` era
2003-10-16 7:59 ` era
2003-10-17 8:52 ` era
-- strict thread matches above, loose matches on Subject: below --
2005-10-05 0:25 Eric J Russell
2005-10-05 22:45 ` Richard M. 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=3F8AD296.7010803@yahoo.com \
--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).