From: Julian Graham <joolean@gmail.com>
Subject: Re: About cleaning up the thread stuff
Date: Tue, 18 Jan 2005 13:03:56 -0500 [thread overview]
Message-ID: <2bc5f82105011810033f18dec5@mail.gmail.com> (raw)
In-Reply-To: <ljy8eqy8n5.fsf@troy.dt.e-technik.uni-dortmund.de>
I like that, but only because I could never figure out how to use
dynamic roots. ;)
Re: your other points,
So what will happen if you build Guile without the threading stuff?
Are the thread procedures (e.g., 'make-thread',
'call-with-new-thread', etc.) simply not made visible?
When you say that any thread may enter guile-mode, do you mean that
the prohibition against more than one thread of C code making calls to
Guile's API is being lifted?
Also, let me know if you'd like me to tweak that thread-cancellation
patch I sent in a few months ago to reflect the changes you're talking
about. (Or maybe you'd prefer to write it from scratch yourself?)
Cheers,
Julian
On Tue, 18 Jan 2005 18:00:46 +0100, Marius Vollmer
<marius.vollmer@uni-dortmund.de> wrote:
> First radical thing: dynamic roots will go... their function will be
> taken over by thread structure directly. Good idea?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-01-18 18:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 15:54 About cleaning up the thread stuff Marius Vollmer
2005-01-18 17:00 ` Marius Vollmer
2005-01-18 18:03 ` Julian Graham [this message]
2005-01-18 21:03 ` Marius Vollmer
2005-01-18 18:08 ` Andy Wingo
2005-01-18 21:04 ` Marius Vollmer
2005-01-18 22:02 ` Kevin Ryde
2005-01-18 23:05 ` Marius Vollmer
2005-01-19 0:02 ` Kevin Ryde
2005-02-01 16:02 ` Marius Vollmer
2005-03-02 21:09 ` Marius Vollmer
2005-03-04 0:46 ` Kevin Ryde
2005-03-04 11:33 ` 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=2bc5f82105011810033f18dec5@mail.gmail.com \
--to=joolean@gmail.com \
/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).