This is the mail archive of the guile@cygnus.com mailing list for the guile project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Jim Blandy <jimb@red-bean.com> writes: > I think Guile will not work happily in multi-threaded programs at all, > because creating a thread creates a new stack, Guile needs to know > about any stack that might hold heap references. Too bad ... even for very simple functionalities ? For instance, I'm trying to integrate Guile in a multi-threaded program to provide functions that I want the user to customize instead of hard-coding them. After parsing a (guile) configuration file, I get several SCM objects which are very simple functions, like (lambda (x) (+ 2.0 x)). Then, several threads might call their own function at any time. Won't this work either ? I tried it yesterday, and I got very quickly a guile stack overflow. Is this problem related to the former one ? The point is that my functions are very simple, but might be called very often (like 30 times per second). -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna@inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19