[Ecls-list] Poll about removal of a feature

Juan Jose Garcia-Ripoll juanjose.garciaripoll at googlemail.com
Wed Feb 3 21:50:38 UTC 2010


... if it can be called so.

SBCL has opted to make all make all structures unprotected against
concurrent access. That means hashtables, arrays, and other structures have
to be managed by the user taking into account the fact that different
threads may try to read / write to them. In other words, those structures do
not have mutexes, locks, semaphores, etc.

I would like to copy that idea in ECL, cleaning up and simplifying the
hashtables code.

Anybody is against it? Why?

Juanjo

-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20100203/a65c0fec/attachment.html>


More information about the ecl-devel mailing list