unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: About removing the low level thread API
Date: Tue, 19 Apr 2005 16:30:00 -0500	[thread overview]
Message-ID: <87vf6ie9pj.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <ljis48ya48.fsf@troy.dt.e-technik.uni-dortmund.de> (Marius Vollmer's message of "Thu, 03 Mar 2005 17:20:23 +0100")

Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:

> I want to remove scm_mutex_lock (and all other functions in the
> low-level API) and maybe, just maybe, provide instead
>
>   - int scm_p_pthread_mutex_lock (scm_p_pthread_mutex_t *mutex)
>   Identical to pthread_mutex_lock on systems with pthreads and when
>   Guile has been configured --with-thtreads; otherwise, does nothing
>   and always returns 0.
>
> Would you say that such alias for the pthreads API is useful?
>
> Guile needs it internally anyway, but when we do not export it, we can
> just implement what we need and can change it at will, of course.

Unless there's a strong case, I don't think we should export it.  We
can always be convinced to export it later, but it's much more
difficult to "unexport" something.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  parent reply	other threads:[~2005-04-19 21:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 16:20 About removing the low level thread API Marius Vollmer
2005-03-04  0:48 ` Kevin Ryde
2005-04-18 22:51 ` Kevin Ryde
2005-04-19 21:30 ` Rob Browning [this message]
2005-04-20 22:35 ` 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=87vf6ie9pj.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@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).