From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: a little puzzle
Date: Fri, 08 Oct 2010 19:14:34 +0200 [thread overview]
Message-ID: <m3sk0gfvyd.fsf@unquote.localdomain> (raw)
Put this in your REPL and smoke it:
(define* (make-me-a-socket #:key
(host #f)
(addr (if host (inet-aton host) INADDR_LOOPBACK))
(port 37146))
(let ((server (socket PF_INET SOCK_STREAM 0)))
(setsockopt server SOL_SOCKET SO_REUSEADDR 1)
(bind server AF_INET addr port)
(listen server 5)
server))
(sigaction SIGINT (lambda (sig) (throw 'foo)))
(define s (make-me-a-socket))
(accept s) ; Now Ctrl-C
What do you expect to happen here?
Probably not this:
ERROR: In procedure accept:
ERROR: Interrupted system call
Entering a new prompt. Type `,bt' for a backtrace or `,q' to continue.
scheme@(guile-user) [1]>
Throw to key `foo' with args `()' while reading expression.
scheme@(guile-user) [1]>
That's right: two throws for the price of one! The interrupted syscall,
and then the asynchronous signal. Fun...
Andy
--
http://wingolog.org/
next reply other threads:[~2010-10-08 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 17:14 Andy Wingo [this message]
2010-10-08 17:32 ` a little puzzle Andy Wingo
2010-10-10 14:58 ` Andy Wingo
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=m3sk0gfvyd.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-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).