From: Damien Mattei <damien.mattei@gmail.com>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: match error
Date: Wed, 2 Aug 2023 08:52:13 +0200 [thread overview]
Message-ID: <CADEOadeTzLhgazZpAgYfR+CFq1JDcHoJne3F_h0p7rFF1W3tMg@mail.gmail.com> (raw)
In-Reply-To: <277500eb274be46b6daae245fa383ff08be83b6e.camel@abou-samra.fr>
yes i read the section of NEWS:
https://git.savannah.gnu.org/cgit/guile.git/tree/NEWS?h=v3.0.9#n8
** Cross-module inlining
"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 have few modules only 2 : Scheme+ and the program that is written in
Scheme+ (different than in Racket because Guile have built-in support
for SRFI105 curly-infix and Racket no ,so each time i want to use
SRFI105 reader i need to put the code in a new module) i admit i could
use more module style in Guile too...
i recurently (happens 2 times a year only...) being forced to swap out
all .o files but it is not previsible when.
On Tue, Aug 1, 2023 at 11:17 PM Jean Abou Samra <jean@abou-samra.fr> wrote:
>
> it seems the cleaning of old .o files solved the problem
>
>
>
> Might be related to cross-module inlining then (just a wild guess, but it can be really treacherous; see Guile's NEWS file if you didn't know about it).
next prev parent reply other threads:[~2023-08-02 6:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 9:53 (unknown) Damien Mattei
2023-08-01 9:59 ` Jean Abou Samra
2023-08-01 10:46 ` Re: Damien Mattei
2023-08-01 11:46 ` Re: Jean Abou Samra
2023-08-01 14:28 ` match error Damien Mattei
2023-08-01 17:32 ` Damien Mattei
2023-08-01 21:16 ` Jean Abou Samra
2023-08-02 6:52 ` Damien Mattei [this message]
2023-08-01 10:57 ` message without subject Zelphir Kaltstahl
2023-08-01 13:46 ` match error Damien Mattei
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=CADEOadeTzLhgazZpAgYfR+CFq1JDcHoJne3F_h0p7rFF1W3tMg@mail.gmail.com \
--to=damien.mattei@gmail.com \
--cc=guile-user@gnu.org \
--cc=jean@abou-samra.fr \
/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).