From: Marius Vollmer <mvo@zagadka.de>
Cc: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Subject: Re: SCM_DEFER_INTS versus error
Date: Mon, 22 Sep 2003 20:10:38 +0200 [thread overview]
Message-ID: <87oexcd78h.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87r82bxbx0.fsf@zip.com.au> (Kevin Ryde's message of "Sun, 21 Sep 2003 09:44:43 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> Marius Vollmer <mvo@zagadka.de> writes:
>>
>> Right now (if I'm still uptodate), only one thread can
>> execute 'in Guile',
>
> Oh, I thought you'd said previously there could be concurrent such
> threads. (I'd meant to try to work up a section for the manual on
> such things.)
What are you referring to precisely? We do use concurrent threads,
but we (currently) restrict them to cooperate so that only one of them
has access to Guile data structures at any one time. (We have the
equivalent of the Big Kernel Lock.) When a thread might block or has
executed long enough, it leaves Guile-mode temporarily, allowing the
next thread to execute.
(I think. I have to admit, that I am probably not fully uptodate with
the details, as Mikael has done the most work on this.)
>> Yes.
>
> I realized since posting, that time() on a DOS system might be
> affected by the TZ changes made by the other stime.c functions.
>
> I guess all that stuff ought to change to use a little mutex
> controlling access to TZ. getenv/putenv would have to cooperate with
> that too so a mere temporary change is not seen or overridden.
Blech.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-09-22 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 1:37 SCM_DEFER_INTS versus error Kevin Ryde
2003-09-17 22:58 ` Marius Vollmer
2003-09-19 20:34 ` Tom Lord
2003-09-22 18:01 ` Marius Vollmer
2003-09-20 23:44 ` Kevin Ryde
2003-09-22 18:10 ` Marius Vollmer [this message]
2003-09-23 1:01 ` Mikael Djurfeldt
2003-10-07 17:54 ` Marius Vollmer
2003-12-06 21:15 ` Kevin Ryde
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=87oexcd78h.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--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).