unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: rixed@happyleptic.org
Cc: 12459@debbugs.gnu.org
Subject: bug#12459: Strange issue with circular dependancies
Date: Fri, 23 Nov 2012 23:44:49 +0100	[thread overview]
Message-ID: <873900ey72.fsf@gnu.org> (raw)
In-Reply-To: <20120917114808.GA3394@securactive.lan> (rixed@happyleptic.org's message of "Mon, 17 Sep 2012 13:48:08 +0200")

Hi,

rixed@happyleptic.org skribis:

> While the compiler does manage most circular dependancies, some cases still
> cannot be compiled.

It’s really not supposed to work, neither at compile time nor at run time.

Sometimes it turns out to work “by chance” as in this case, or because
there are autoloads to defer the cycle.  But in general, it should
really be avoided.

Won’t fix?  :-)

Ludo’.





  reply	other threads:[~2012-11-23 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-17 11:48 bug#12459: Strange issue with circular dependancies rixed
2012-11-23 22:44 ` Ludovic Courtès [this message]
2012-11-26  8:54   ` rixed
2012-11-27 21:38     ` Ludovic Courtès

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=873900ey72.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=12459@debbugs.gnu.org \
    --cc=rixed@happyleptic.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).