From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: Trigger action at exit?
Date: Mon, 03 Mar 2008 20:44:28 +0000 [thread overview]
Message-ID: <87hcfna66r.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87ve459gxb.fsf@gnu.org> (Ludovic Courtès's message of "Sun, 02 Mar 2008 18:25:36 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> "John Trammell" <johntrammell@gmail.com> writes:
>
>> After a little searching I've stumbled across "add-hook! exit-hook
>> ...", but for the life of me I can't seem to get it to do what I want.
>> Here's a taste of what I'm looking for:
>>
>> (define foo (lambda () (display "foo") (newline)))
>> (add-hook! exit-hook foo)
>> (run-hook exit-hook)
>>
>> I'd like something like this, that doesn't need the explicit
>> "run-hook" at the end. Ideas?
>
> `exit-hook' is only run by the REPL, so it's not useful in programs.
>
> One possibility is to catch the `quit' exception:
>
> guile> (catch 'quit
> (lambda ()
> ;; the function that may `exit'
> (exit 1))
> (lambda (key . args)
> ;; the handler
> (format #t "quit: ~a~%" args)))
> quit: (1)
In the light of this thread, and another one about atexit in AutoGen,
perhaps we should look at providing a Scheme-level at-exit primitive?
The main point, I think, would be to guarantee that anything
registered by (at-exit ...) or scm_at_exit (...) would run _before_
Guile starts doing its own cleanups.
Regards,
Neil
next prev parent reply other threads:[~2008-03-03 20:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 22:30 Trigger action at exit? John Trammell
2008-03-02 17:25 ` Ludovic Courtès
2008-03-03 20:44 ` Neil Jerram [this message]
2008-03-03 21:53 ` Ludovic Courtès
2008-03-03 22:17 ` Neil Jerram
2008-03-04 10:25 ` Ludovic Courtès
2008-03-04 17:03 ` John Trammell
2008-03-05 21:14 ` Neil Jerram
2008-03-03 21:22 ` John Trammell
2008-03-03 21:40 ` Ludovic Courtès
2008-03-03 22:27 ` John Trammell
2008-03-05 21:27 ` Neil Jerram
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=87hcfna66r.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-user@gnu.org \
--cc=ludo@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).