Scribit Ian Eslick dies 20/01/2007 hora 16:54:
> Does anyone have a better suggestion here? For example is there a
> portability layer that can detect the current thread ID and use that
> to index the default global values?
http://trac.common-lisp.net/bordeaux-threads/wiki/ApiDocumentation#curren
Scribit Robert L. Read dies 20/01/2007 hora 14:06:
> I personally solve problem by using SBCL mutexes around the
> serialize/deserialize code, but I have not committed that code, since
> it is highly SBCL-specific, and in fact I don't know of a good way to
> do locking portably.
I used the bordeux
On Saturday 20 January 2007 22:54, Ian Eslick wrote:
> There should be an e-mail about this in the archive somewhere, but to
> summarize...
>
> I think that requiring client code to worry about wrapping every
> thread in run-elephant-thread is unrealistic, so that interface is
> now deprecated. Th
There should be an e-mail about this in the archive somewhere, but to
summarize...
I think that requiring client code to worry about wrapping every
thread in run-elephant-thread is unrealistic, so that interface is
now deprecated. The reason for this is simple, when you are using a
multi
Ian is working on this; I think significant progress will be made when
he finishes his check-in.
The biggest problem is that serializer uses globals in such a way that
it is not thread-safe;
Ian is specifically rewriting that.
I personally solve problem by using SBCL mutexes around the
serialize/
