From: Danny Milosavljevic <dannym@scratchpost.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Trouble with circular module dependencies (Re: 01/02: gnu: Add ncurses-with-gpm.)
Date: Tue, 25 Jul 2017 23:59:17 +0200 [thread overview]
Message-ID: <20170725235917.012fb93b@scratchpost.org> (raw)
In-Reply-To: <877eyyyes0.fsf_-_@netris.org>
Hi Mark,
On Sun, 23 Jul 2017 18:22:39 -0400
Mark H Weaver <mhw@netris.org> wrote:
> any of us could make, invited by our IMO questionable practice of
> allowing cyclic module dependencies, and not sufficiently mitigated by
> warnings about this issue.
Sorry!
It was actually caused by me trying to avoid a dependency of (gnu packages ncurses) to (gnu packages linux). But in trying to avoid it I made it worse.
I have to say this circular dependency stuff is quite... strange. I'm not sure what it helps to have it in Guile at all.
But thanks for the explanation. I've also looked at libguile/modules.c where it indeed first creates an empty module and only then resolves the imports (scm_c_define_module).
I've worked with languages which explicitly disallow module circular dependencies (Pascal etc) and it's not been constraining to me - on the contrary, it makes me better visualize which modules are more fundamental (in my reductionist worldview of a program).
prev parent reply other threads:[~2017-07-25 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170715081544.12288.82778@vcs0.savannah.gnu.org>
[not found] ` <20170715081545.DB2A022E4F@vcs0.savannah.gnu.org>
2017-07-23 22:22 ` Trouble with circular module dependencies (Re: 01/02: gnu: Add ncurses-with-gpm.) Mark H Weaver
2017-07-24 6:37 ` Ricardo Wurmus
2017-07-24 9:25 ` Ludovic Courtès
2017-07-25 21:28 ` Ricardo Wurmus
2017-07-25 21:45 ` Danny Milosavljevic
2017-07-26 7:30 ` Alex Sassmannshausen
2017-07-27 9:01 ` Ludovic Courtès
2017-07-25 21:59 ` Danny Milosavljevic [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170725235917.012fb93b@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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/guix.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).