From: Olivier Dion via "Developers list for Guile, the GNU extensibility library" <guile-devel@gnu.org>
To: Andy Wingo <wingo@pobox.com>, Andy Wingo <wingo@pobox.com>,
guile-user@gnu.org, guile-sources@gnu.org, guile-devel@gnu.org,
info-gnu@gnu.org
Subject: Re: [PP?] GNU Guile 3.0.8 released
Date: Fri, 11 Feb 2022 09:34:04 -0500 [thread overview]
Message-ID: <87leyhlbfn.fsf@laura> (raw)
In-Reply-To: <87zgmxn8t7.fsf@pobox.com>
On Fri, 11 Feb 2022, Andy Wingo <wingo@pobox.com> wrote:
> Note however that as with macros, when a definition changes in module
> A, a separately compiled module B that uses that definition doesn't
> automatically get recompiled. This is a limitation in Guile that we
> would like to fix.
I find this to be critical. It's a real pain to not have dependencies
tracking in a build system.
How could this be fixed? Does generating *.d files like GCC does for C
would work?
--
Olivier Dion
Polymtl
prev parent reply other threads:[~2022-02-11 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 7:47 GNU Guile 3.0.8 released Andy Wingo
2022-02-11 11:05 ` Maxime Devos
2022-02-11 17:14 ` Aleix Conchillo Flaqué
2022-02-11 18:03 ` Ricardo Wurmus
2022-02-12 1:28 ` Greg Troxel
2022-02-12 2:04 ` Aleix Conchillo Flaqué
2022-02-11 14:34 ` Olivier Dion via Developers list for Guile, the GNU extensibility library [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://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=87leyhlbfn.fsf@laura \
--to=guile-devel@gnu.org \
--cc=guile-sources@gnu.org \
--cc=guile-user@gnu.org \
--cc=info-gnu@gnu.org \
--cc=olivier.dion@polymtl.ca \
--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).