unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mikael@djurfeldt.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Mailer <vine24683579@gmail.com>,
	guile-devel <guile-devel@gnu.org>,
	 Mikael Djurfeldt <mikael@djurfeldt.com>
Subject: Re: [PATCH] At-exit hook
Date: Fri, 8 Nov 2024 10:09:00 +0100	[thread overview]
Message-ID: <CAA2XvwKqv0qhDuvdJkO=gRfNGytSNb+SYAduCB5M=Wkj7Gfz-w@mail.gmail.com> (raw)
In-Reply-To: <20241107231810.ZyJA2D00E42S6aw01yJAnr@laurent.telenet-ops.be>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

Hi all,

I've come to the conclusion that this problem is unsolvable and I will
abandon the idea of an at-exit-hook. The most serious potential consequence
of running it in really_cleanup_for_exit(), which is indirectly invoked
through atexit(), is that the resources to clean up or the Guile library
itself has already been deallocated.

Also, calling it from scm_boot_guile is a half measure since the
application might exit from main_func(). I thank Chris and Maxime for
pointing out the problems.

I actually think that I tried to do this (introduce an at-exit-hook) 25
years ago, with the same eventual realizations, but didn't recall that at
first. Brace for 2050! :-))

Best regards,
Mikael

[-- Attachment #2: Type: text/html, Size: 860 bytes --]

      reply	other threads:[~2024-11-08  9:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-06 19:52 [PATCH] At-exit hook Mikael Djurfeldt
2024-11-07 11:23 ` Maxime Devos
2024-11-07 12:08   ` Nala Ginrut
2024-11-07 12:09   ` Mailer
2024-11-07 12:27     ` Mailer
2024-11-07 13:28       ` Mikael Djurfeldt
2024-11-07 16:10     ` Maxime Devos
2024-11-07 19:51       ` Mailer
2024-11-07 22:18         ` Maxime Devos
2024-11-08  9:09           ` Mikael Djurfeldt [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='CAA2XvwKqv0qhDuvdJkO=gRfNGytSNb+SYAduCB5M=Wkj7Gfz-w@mail.gmail.com' \
    --to=mikael@djurfeldt.com \
    --cc=guile-devel@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=vine24683579@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).