unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: new-model.text, please comment
Date: Fri, 13 Sep 2002 15:34:24 -0500	[thread overview]
Message-ID: <87r8fxy6gf.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87sn0dr66s.fsf@zagadka.ping.de> (Marius Vollmer's message of "13 Sep 2002 22:22:03 +0200")

Marius Vollmer <mvo@zagadka.ping.de> writes:

> Yes, this is what I had in mind.  Without this :module-barrier
> statement, the compiler would have to assume that any call can
> change the module setup (which will make a lot optimizations
> impossible).  Or we would have to have a different kind of module
> system.
>
> We could have also use declarations to communicate the module
> barrier to the compiler.  I.e., the variable named
> do-something-that-changes-the-current-module! has a declaration that
> the compiler understands.

OK, pretty much what I expected, just wanted to make sure.

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-09-13 20:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 18:05 new-model.text, please comment Marius Vollmer
2002-09-12 22:48 ` Tom Lord
2002-09-14 22:48   ` Marius Vollmer
2002-09-15  0:50     ` Tom Lord
2002-09-15  0:55     ` Tom Lord
2002-09-21 20:27       ` Marius Vollmer
2002-09-12 23:28 ` Rob Browning
2002-09-13 20:22   ` Marius Vollmer
2002-09-13 20:34     ` Rob Browning [this message]
2002-09-13 18:53 ` Neil Jerram
2002-09-13 22:06   ` Rob Browning
2002-09-14  1:15     ` Lynn Winebarger
2002-09-14 22:05   ` Marius Vollmer

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=87r8fxy6gf.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@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).