unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Christopher Cramer <crayc@pyro.net>
Cc: guile-devel@gnu.org
Subject: Re: Redoing conditional thread support
Date: Mon, 14 Oct 2002 23:35:22 -0500	[thread overview]
Message-ID: <20021014233522.A13138@kiwi.pyrotechnics.com> (raw)
In-Reply-To: <ljzntmjqju.fsf@burns.dt.e-technik.uni-dortmund.de>; from marius.vollmer@uni-dortmund.de on Thu, Oct 10, 2002 at 04:51:01PM +0200

On Thu, Oct 10, 2002 at 04:51:01PM +0200, Marius Vollmer wrote:
> I'm about to reorganize our conditional threading stuff so that there
> is always a thread API (scm_current_thread, scm_call_with_new_thread,
> mutices, condition variables, etc), but when you configure
> "--without-threads" you get a null-thread implementation that doesn't
> allow the creation of new threads.  Thus there will always be only a
> single thread.

I assume scm_call_with_new_thread without threads would work like
scm_catch? And I guess trying to lock a mutex that's already locked
would give an exception.

-- 
Christopher Cramer <crayc@pyro.net> <http://www.pyro.net/~crayc/>
"Gore would have finished ahead by the barest of margins had he pursued
and gained a complete statewide recount." -- Associated Press, 9/6/2002


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


  parent reply	other threads:[~2002-10-15  4:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10 14:51 Redoing conditional thread support Marius Vollmer
2002-10-11 21:37 ` Neil Jerram
2002-10-11 22:49   ` Marius Vollmer
2002-10-12 19:38     ` Neil Jerram
2002-10-15  4:35 ` Christopher Cramer [this message]
2002-10-15 10:43   ` Marius Vollmer
2002-10-15 13:00 ` Mikael Djurfeldt
2002-10-15 18:28   ` Marius Vollmer

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=20021014233522.A13138@kiwi.pyrotechnics.com \
    --to=crayc@pyro.net \
    --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).