From: Kevin Ryde <user42@zip.com.au>
Subject: SCM_DEFER_INTS in 1.6
Date: Sat, 22 Apr 2006 09:55:32 +1000 [thread overview]
Message-ID: <8764l2iivf.fsf@zip.com.au> (raw)
What does SCM_DEFER_INTS actually do in 1.6? I'm looking at the way
guile-gtk 1.2 puts it around gtk/gdk function calls, but I couldn't
spot anything in it which seemed relevant.
scm_ints_disabled gets set, but I couldn't see anywhere that variable
is tested, only take_signal() where it suppresses an SCM_NEWCELL (and
the result of that newcell seems unused anyway).
I'm wondering if the right thing would be just to drop the
SCM_DEFER_INTS from the guile-gtk generated code. (The code there may
still want a mutex then, but that's a gtk/gdk matter, unrelated to
what guile might or might not need.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2006-04-21 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 23:55 Kevin Ryde [this message]
2006-05-02 8:30 ` SCM_DEFER_INTS in 1.6 Ludovic Courtès
2006-05-03 1:34 ` Kevin Ryde
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=8764l2iivf.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).