unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Modules with Circular Dependencies
Date: Fri, 18 Mar 2011 17:16:14 -0400	[thread overview]
Message-ID: <AANLkTi=pMfdfUS8Ci=O7KrKBZB0Z7hEJ8BJyTL_3OjkF@mail.gmail.com> (raw)
In-Reply-To: <87y64c2m4q.fsf@gnu.org>

Hello,

> The problem is that modules are resolved at compile-time, in addition to
> run-time, so there just can’t be circular dependencies.

It's true that a module couldn't depend, at compile-time, on a module
that was only available at run-time. However, I think we could handle
circular dependencies as long as all of the modules involved were
available at compile-time. I would even say that this is one more
instance of the general principle that people shouldn't have to do
things that computers are able to do for them - in this case, you
shouldn't have to manually order your syntax definitions and uses when
your computer can do a graph search for you.

> Besides, I think it’s generally a problem from an engineering viewpoint
> when cycles are introduced.

This sounds like it could be true, but it's so general I don't know
how to respond. Could you talk more about it, or give an example?

> So my feeling is that Guile should be able to detect cycles and warn
> users.

Yes, at a minimum cycle detection would be good.

Noah



  reply	other threads:[~2011-03-18 21:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 18:15 Modules with Circular Dependencies Noah Lavine
2011-03-18 20:45 ` Ludovic Courtès
2011-03-18 21:16   ` Noah Lavine [this message]
2011-03-24 21:50     ` Andy Wingo

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=pMfdfUS8Ci=O7KrKBZB0Z7hEJ8BJyTL_3OjkF@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).