unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mikael Djurfeldt <mdj@kvast.blakulla.net>
Cc: djurfeldt@nada.kth.se
Subject: Re: C level threads...
Date: Mon, 02 Dec 2002 12:43:59 +0100	[thread overview]
Message-ID: <xy7fztgzlvk.fsf@linnaeus.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <xy7r8d0zv4k.fsf@linnaeus.i-did-not-set--mail-host-address--so-tickle-me> (Mikael Djurfeldt's message of "Mon, 02 Dec 2002 09:24:11 +0100")

A further point:

I think you originally aimed for the Guile "disguise" of the pthread
API to be so close to the pthread API that it introduces zero
overhead.

But if you:

#define scm_mutex_lock(mx)    pthread_mutex_lock (mx)

guile-gtk-1.2 can't plug in scm_mutex_lock into glib's thread
interface.

Why can't we just keep the API as it has been the last few years?

According to the original API, the entries should be functions or
function pointers.  Then the above should be:

#define scm_mutex_init    pthread_mutex_init
#define scm_mutex_destroy pthread_mutex_destroy
#define scm_mutex_lock    pthread_mutex_lock

etc.

Can't we simply adhere to the old API without incompatible changes?


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


  reply	other threads:[~2002-12-02 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-02  1:30 C level threads Marius Vollmer
2002-12-02  8:24 ` Mikael Djurfeldt
2002-12-02 11:43   ` Mikael Djurfeldt [this message]
2002-12-02 17:27   ` Marius Vollmer
2002-12-02 12:57 ` 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=xy7fztgzlvk.fsf@linnaeus.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mdj@kvast.blakulla.net \
    --cc=djurfeldt@nada.kth.se \
    /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).