[elephant-devel] run-elephant-thread

[Pierre THIERRY]

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-threads to do that, I attach the patch I personnaly
used. It works like a charm as far as I can see, but as I'm not that
familiar with Elephant's internals, I can't tell if everything is indeed
correctly protected. My applications using it were only put under
moderate workload.

Avoid globals is a Good Thing anyway, and hopefully 0.6.1 will be both
thead-safe and efficient (the lock solution adds a major bottleneck...).

Portably,
Pierre
-- 
nowhere.man at levallois.eu.org
OpenPGP 0xD9D50D8A
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mutex.diff
Type: text/x-diff
Size: 4607 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/elephant-devel/attachments/20070121/e48e9bda/attachment.diff>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://mailman.common-lisp.net/pipermail/elephant-devel/attachments/20070121/e48e9bda/attachment.sig>