[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 1.6 and pthreads [Re: Why doesn't gh_enter() return?]

From: Alejandro Forero Cuervo
Subject: Re: 1.6 and pthreads [Re: Why doesn't gh_enter() return?]
Date: Sun, 13 May 2001 10:33:30 -0500
User-agent: Mutt/1.2.5i
User-agent: Mutt/1.2.5i

    nothing prevents you from using Guile in a pthread application,
    provided that you call into Guile from no more than one thread


Does this mean I can just add a mutex around the Guile-calling code
and just forget about it?  I mean, it doesn't matter if all threads do
call functions in Guile, as long as they don't call them
simultaneously, right?  Or am I misunderstanding you and do you really
mean only one given thread can call functions from Guile, that if a
given thread calls functions in Guile, no other threads can do it?
Hmm, I really don't know about its internals, but having multiple
stacks must make things hard for Guile's garbage collector.

Btw, gh_eval and gh_eval_str are reentrant, right?  If I call gh_eval,
and it happens to call my C code, I am allowed to call gh_eval there,
right?  If so, are any functions there not reentrant?

Any plans of making it possible to call it from multiple threads
simultaneously?  I'm afraid that would be required for my pthreaded
application server... :/



The mere formulation of a problem is far more essential than its solution.
      -- Albert Einstein.

$0='!/sfldbi!yjoV0msfQ!sfiupob!utvK'x44;print map{("\e[7m \e[0m",chr ord
"219CC1CCC033E7E660198CCE4E66798303873CCE60F3387$F"#Don't you love Perl?

Attachment: pgp20J6SbX0B3.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]