From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Subject: Re: guile threading deadlock
Date: Mon, 10 Nov 2008 00:36:58 +0100 [thread overview]
Message-ID: <874p2ga2ud.fsf@gnu.org> (raw)
In-Reply-To: 3ae3aa420811091416s3f6ebd7vc49a9f8c8278ced9@mail.gmail.com
Hello Linas,
"Linas Vepstas" <linasvepstas@gmail.com> writes:
> However, there is a simple solution: wrap every call
> to scm_c_eval_string() with a call to scm_with_guile().
> Doesn't seem very optimal or pretty, but it works.
Cool.
> In particular, any thread that uses scm_init_guile cannot
> sleep -- this should be stated up front. Any thread that
> is "in guile mode" cannot sleep. This too should be stated
> up front.
Again, it *is* documented, but maybe not sufficiently prominently, or
maybe it could be repeated in other places of the manual. Can you say
specifically how you'd like to change that?
> Here's my point of view, ... I've got a PhD, I've been coding
> for decades; my last job was as a linux kernel programmer,
> doing close-to-the-hardware work
Great, congratulations! :-)
>> Do you have any suggestions to clarify that?
>
> Well, yes. But it would perhaps be easiest for me
> to write the text myself, rather than explain how the
> text could be written.
Good, that's what I was suggesting.
> Well, if I provided patch files, would that work? Where would
> I send these? Who maintains this stuff?
Please send patches to <bug-guile@gnu.org>. If they are non-trivial,
you'll need to assign copyright to the FSF, but we can work this out
off-line in due time.
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-11-09 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 2:26 guile threading deadlock Linas Vepstas
2008-11-08 12:25 ` Ludovic Courtès
2008-11-08 18:29 ` Linas Vepstas
2008-11-09 17:13 ` Ludovic Courtès
2008-11-09 19:47 ` Linas Vepstas
2008-11-09 21:14 ` Ludovic Courtès
2008-11-09 22:16 ` Linas Vepstas
2008-11-09 23:36 ` Ludovic Courtès [this message]
2008-11-10 23:59 ` Linas Vepstas
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=874p2ga2ud.fsf@gnu.org \
--to=ludo@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).