From: <dsmich@roadrunner.com>
To: Andy Wingo <wingo@pobox.com>, Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: GNU Guile branch, master, updated. v2.1.0-102-g0f9f51a
Date: Sat, 14 Jan 2012 22:01:11 +0000 [thread overview]
Message-ID: <20120114220111.RGTB8.49972.root@cdptpa-web12-z01> (raw)
In-Reply-To: <87hazy58ct.fsf@netris.org>
---- Mark H Weaver <mhw@netris.org> wrote:
> There's another option: we could properly track the compile-time
> dependencies of each module, and automatically consider a .go file stale
> if _any_ of its compile-time dependencies are newer than it.
>
> To be more specific: I think we need to record, in every syntax
> transformer bound at top-level, the name of the module where it's bound.
> Then, within the dynamic extent of `compile-file', (probably using a
> fluid) we'd need to accumulate the set of modules whose macro
> transformers are used during compilation of the file. This set of
> modules (the compile-time dependencies) would be included in the .go
> file.
I think we should have this.
-Dale
next prev parent reply other threads:[~2012-01-14 22:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1RNMul-0000TQ-6L@vcs.savannah.gnu.org>
2011-11-10 4:36 ` GNU Guile branch, master, updated. v2.1.0-102-g0f9f51a Mark H Weaver
2011-11-10 8:34 ` Andy Wingo
2011-11-10 16:46 ` Mark H Weaver
2011-11-11 20:20 ` Ludovic Courtès
2011-11-15 20:58 ` Andy Wingo
2011-11-15 21:12 ` Andy Wingo
2011-11-16 3:58 ` Mark H Weaver
2012-01-06 17:47 ` Andy Wingo
2012-01-14 20:37 ` Mark H Weaver
2012-01-14 20:54 ` David Kastrup
2012-01-14 21:39 ` Mark H Weaver
2012-01-14 22:01 ` dsmich [this message]
2012-01-14 23:40 ` Ludovic Courtès
2012-01-15 11:44 ` 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=20120114220111.RGTB8.49972.root@cdptpa-web12-z01 \
--to=dsmich@roadrunner.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=wingo@pobox.com \
/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).