Re: [Off Topic] Re: Reconciling Emacs Lisp and Scheme
sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes:
Didier> and seems to be usable in multi-threaded apps.
I don't know what you mean by this, but it's wrong by almost any
definition.
In Elk, the garbadge collector acts ala emacs: you inform it
explicitely of any objects that should be protected with GC_Link(). Even if
it's a PITA to have to protect by hand the scheme objects, the advantage is
that different threads can create and protect scheme objects easily. On the
contrary, there's no explicit GC protection in guile. Consequently, guile will
know only the main program stack and objects created by subsequent threads
won't be caugth by the GC.
Elk is not thread-safe and it does not provide a thread library.
Does this mean that I can't safely have different threads calling
scheme functions in parallel, even if those functions don't use or affect
global objects ?
--
/ / _ _ 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