From: Kevin Ryde <user42@zip.com.au>
Subject: Re: SCM_DEFER_INTS in 1.6
Date: Wed, 03 May 2006 11:34:32 +1000 [thread overview]
Message-ID: <87r73b99hz.fsf@zip.com.au> (raw)
In-Reply-To: <87irooeslr.fsf@laas.fr> (Ludovic Courtès's message of "Tue, 02 May 2006 10:30:40 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> I think what you see gets generated by G-Wrap.
Actually in guile-gtk 1.2 it's the old way with the build script
thingie.
> Whatever `SCM_DEFER_INTS' actually does, I can't see any reason why
> G-Wrap should issue it as it does, and I've been tempted to remove
> it from there.
Yep.
> I don't think it even needs to be replaced by a mutex or some such.
Well, gtk isn't reentrant so it needs some care. I'm thinking to
leave it to the application. But that's a subject for the guile-gtk
list.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2006-05-03 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 23:55 SCM_DEFER_INTS in 1.6 Kevin Ryde
2006-05-02 8:30 ` Ludovic Courtès
2006-05-03 1:34 ` Kevin Ryde [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=87r73b99hz.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).