From: hector <hectorlahoz@gmail.com>
To: help-gnu-emacs@gnu.org
Cc: john.b.mastro@gmail.com
Subject: Re: unexpected byte-compiler behaviour
Date: Thu, 9 Mar 2017 23:49:45 +0100 [thread overview]
Message-ID: <20170309224944.GA3148@workstation> (raw)
In-Reply-To: <CAOj2CQS0oZYacL+GPeT8x1_nEvfVgSEJ6AOfzMr=QRhzfPVg0Q@mail.gmail.com>
On Thu, Mar 09, 2017 at 01:55:12PM -0800, John Mastro wrote:
> Functions do need to be defined before they're called, just not before
> the call is compiled. However, macros (like defclass) are expanded at
> compile time, so they need to be defined before then.
So basically linking is done, not at compilation like in C, but dynamically
at run time. I think I get it. Thanks a lot.
Could it be that my environment (loaded libraries) is affecting compilation?
Is it advisable to run Emacs with -Q?
next prev parent reply other threads:[~2017-03-09 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 17:46 unexpected byte-compiler behaviour hector
2017-03-09 18:18 ` John Mastro
2017-03-09 18:20 ` John Mastro
2017-03-09 19:17 ` hector
2017-03-09 19:25 ` hector
2017-03-09 21:55 ` John Mastro
2017-03-09 22:49 ` hector [this message]
2017-03-09 23:28 ` John Mastro
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=20170309224944.GA3148@workstation \
--to=hectorlahoz@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=john.b.mastro@gmail.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.
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).