unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mdj@kvast.blakulla.net>
Cc: djurfeldt@nada.kth.se,  Ariel Rios <ariel@arcavia.com>,
	guile-devel@gnu.org
Subject: Re: guile-gtk-1.2 working with guile-1.7.0
Date: 10 Nov 2002 17:04:37 -0500	[thread overview]
Message-ID: <xy7isz55bey.fsf@linnaeus.i-did-not-set--mail-host-address--so-shoot-me> (raw)
In-Reply-To: <87d6pdf6d9.fsf@zagadka.ping.de>

Marius Vollmer <mvo@zagadka.ping.de> writes:

> Mikael Djurfeldt <mdj@kvast.blakulla.net> writes:
> 
> > Today I just added the coop-pthreads adaptations because I'd like to
> > try using them.  I thought that maybe some of it could be useful.
> 
> Yes.  Could you make a new patch against guile-gtk-1.2 from Savannah
> once it works for you?

Well, yes, if you think that would be useful I can do that.

> I will commit the missing scm_t_key stuff in a minute and guile-gtk
> _seems_ to work with coop-pthreads without changes...

I'm afraid the guile-gtk I worked against only just seems to work.
There were things that needed change.

Regarding the missing scm_t_key stuff: I hope you saw that I committed
a few definitions to coop-pthreads.h which supplements the now
deprecated C level API so that gtk-threads.c works with it?

I guess what you are referring to is then something else than C level
support for thread-specific data?  Or have you implemented
thread-specific data without using the pthreads interface?  That could
be splightly more efficient, but the question is if it's really worth
it...

> (btw, what about just using glib's thread plugin API?)

That would certainly be a nice option.  However, that would rule out
using cooperative thread libraries, like COOP or GNU Portable Threads.

I promised to post a summary of our telephone conversation.  I've
actually been write a few words now and then.  Perhaps I'll get it out
today.

Best regards,
Mikael


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-11-10 22:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07 14:40 guile-gtk-1.2 working with guile-1.7.0 Mikael Djurfeldt
2002-11-07 20:29 ` Marius Vollmer
2002-11-07 21:59   ` Mikael Djurfeldt
2002-11-10 21:43     ` Marius Vollmer
2002-11-10 22:04       ` Mikael Djurfeldt [this message]
2002-11-10 22:18         ` Marius Vollmer
2002-11-12  3:48       ` Mikael Djurfeldt

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=xy7isz55bey.fsf@linnaeus.i-did-not-set--mail-host-address--so-shoot-me \
    --to=mdj@kvast.blakulla.net \
    --cc=ariel@arcavia.com \
    --cc=djurfeldt@nada.kth.se \
    --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).