Hello Linas, "Linas Vepstas" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>. 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'.
