From: Jean Abou Samra <jean@abou-samra.fr>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>,
Guile User <guile-user@gnu.org>
Subject: Re: Curiosity: Microkernel implemented in Guile ?
Date: Wed, 29 Jun 2022 00:30:28 +0200 [thread overview]
Message-ID: <f149b6db-4147-c300-87fb-7aa953bbb8c1@abou-samra.fr> (raw)
In-Reply-To: <CAPjoZofk0QFrwcA9o7pVq_xxUH2Dak4RNMRMShWMqVE9EpXvPQ@mail.gmail.com>
Le 26/06/2022 à 12:37, Nala Ginrut a écrit :
> OK, let's face the issues, I encountered similar problems like what
> you described.
>
> 1. To avoid the irritating compiling message, I have to use parameters
> to rebind current-error-port.
OK, interesting to know, thanks.
> 2. Sometimes folks compile the Guile code and installed it in a wrong
> load path, so when you run it, it will auto compile everthing again.
This one is a real problem, but not one we're facing in LilyPond.
> 3. The debug information seems broken for a long time, it's not good
> to trace the error. But I don't think it's because of the design of
> Guile, it's broken when Guile had upgraded the VM implementation. It
> was good before that.
Yes. I remember seeing the bug on debbugs, but I can't seem to find it
right now. I recall that Mark H. Weaver commented that interpreted code
went through primitive-eval on traditional expressions (not syntax objects).
Best,
Jean
next prev parent reply other threads:[~2022-06-28 22:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 6:11 Curiosity: Microkernel implemented in Guile ? Matias Jose Seco Baccanelli
2022-06-23 6:57 ` Mikael Djurfeldt
2022-06-23 9:01 ` Ricardo G. Herdt
2022-06-24 5:40 ` Dr. Arne Babenhauserheide
2022-06-23 7:02 ` Dr. Arne Babenhauserheide
2022-06-23 7:32 ` zimoun
2022-06-23 7:34 ` Maxime Devos
2022-07-02 9:47 ` Matias Jose Seco Baccanelli
2022-07-04 2:49 ` Blake Shaw
2022-06-23 9:13 ` pukkamustard
2022-06-23 10:09 ` Nala Ginrut
2022-06-23 11:22 ` Maxime Devos
2022-06-23 15:38 ` Nala Ginrut
2022-06-23 22:03 ` Dr. Arne Babenhauserheide
2022-06-24 1:12 ` Nala Ginrut
2022-06-24 5:45 ` Dr. Arne Babenhauserheide
2022-06-24 7:01 ` Jean Abou Samra
2022-06-24 7:41 ` Dr. Arne Babenhauserheide
2022-06-25 14:35 ` Jean Abou Samra
2022-06-26 6:22 ` Dr. Arne Babenhauserheide
2022-06-26 7:55 ` Ricardo Wurmus
2022-06-26 8:32 ` Dr. Arne Babenhauserheide
2022-06-28 22:23 ` Jean Abou Samra
2022-06-26 10:37 ` Nala Ginrut
2022-06-28 22:30 ` Jean Abou Samra [this message]
2022-06-24 12:42 ` Nala Ginrut
2022-06-24 3:27 ` Ognen Duzlevski
2022-06-24 21:24 ` Dr. Arne Babenhauserheide
2022-06-23 12:13 ` Ognen Duzlevski
2022-06-23 13:30 ` Dr. Arne Babenhauserheide
2022-06-23 17:47 ` Paul Emsley
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=f149b6db-4147-c300-87fb-7aa953bbb8c1@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=arne_bab@web.de \
--cc=guile-user@gnu.org \
--cc=nalaginrut@gmail.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).