From: Maxime Devos <maximedevos@telenet.be>
To: Han-Wen Nienhuys <hanwenn@gmail.com>, Guile Devel <guile-devel@gnu.org>
Cc: lilypond-devel <lilypond-devel@gnu.org>
Subject: Re: Java finalization & smobs?
Date: Fri, 10 Dec 2021 18:02:25 +0000 [thread overview]
Message-ID: <ada42265c42f32cba64d8c4614d8bab4a008c081.camel@telenet.be> (raw)
In-Reply-To: <CAOw_e7afsHz82kyje1tT+=wDk6BnQDO_e6J-E9w-25aa0ozPJA@mail.gmail.com>
Han-Wen Nienhuys schreef op vr 10-12-2021 om 15:59 [+0100]:
> We can change our mark routines to avoid the crash, but it's unclear
> to us if this behavior is intended or not, and we worry that this
> will
> come back to bite us in the future.
> [...]
> [... things about Java-style finalisation ...]
Keep in mind that Jonas Hahnfeld (from LilyPond) was looking into _not_
enabling Java-style finalisation (until guardians are used), see
<https://lists.gnu.org/archive/html/guile-devel/2021-07/msg00000.html>.
Greetings,
Maxime
next prev parent reply other threads:[~2021-12-10 18:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 14:59 Java finalization & smobs? Han-Wen Nienhuys
2021-12-10 18:00 ` Maxime Devos
2021-12-10 18:02 ` Maxime Devos [this message]
2021-12-10 18:10 ` Maxime Devos
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=ada42265c42f32cba64d8c4614d8bab4a008c081.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=hanwenn@gmail.com \
--cc=lilypond-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).