From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: `eval-when-compile' and circular dependencies (was: Re: Source file '.../killer-source.el' newer than byte-compiled file)
Date: Thu, 25 Apr 2019 09:37:17 +0300 [thread overview]
Message-ID: <834l6m1tgi.fsf@gnu.org> (raw)
In-Reply-To: <86imv2epg7.fsf_-_@zoho.eu> (message from Emanuel Berg on Thu, 25 Apr 2019 05:25:28 +0200)
> From: Emanuel Berg <moasenwood@zoho.eu>
> Date: Thu, 25 Apr 2019 05:25:28 +0200
>
> >>> but you will have trouble if you have
> >>> circular dependencies.
> >>
> >> No, I don't have circular dependencies, and
> >> I don't think I can have them, either.
> >> Actually I'm gonna try that right now...
> >>
> >> No, I can't
> >
> > Not easily, no.
>
> Why would you want them?
We don't, it just happens.
> And how do you make it work, if so?
You could look at Eshell as one example, if you really want to
understand. The solution involves using eval-when-compile and its
ilk, I think.
next prev parent reply other threads:[~2019-04-25 6:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 17:39 Source file '.../killer-source.el' newer than byte-compiled file Emanuel Berg
2019-04-23 17:49 ` Eli Zaretskii
2019-04-23 18:32 ` Emanuel Berg
2019-04-23 18:39 ` Emanuel Berg
2019-04-23 19:03 ` Eli Zaretskii
2019-04-23 22:42 ` Emanuel Berg
2019-04-23 23:17 ` Nick Dokos
2019-04-24 0:18 ` Emanuel Berg
2019-04-24 1:33 ` Emanuel Berg
2019-04-24 6:24 ` Eli Zaretskii
2019-04-25 3:25 ` `eval-when-compile' and circular dependencies (was: Re: Source file '.../killer-source.el' newer than byte-compiled file) Emanuel Berg
2019-04-25 6:37 ` Eli Zaretskii [this message]
2019-04-25 7:03 ` Emanuel Berg
2019-04-25 8:43 ` Eli Zaretskii
2019-04-23 19:02 ` Source file '.../killer-source.el' newer than byte-compiled file Eli Zaretskii
2019-04-23 22:59 ` Emanuel Berg
2019-04-23 18:02 ` Emanuel Berg
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=834l6m1tgi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).