[closer-devel] *root-context* and threads
Attila Lendvai
attila.lendvai at gmail.com
Tue Nov 6 14:15:32 UTC 2007
> Due to a hint at comp.lang.lisp, I am not so sure anymore whether this
> is actually a ContextL issue.
>
> Are you sure that my caches cause any problems?
this is most probably an sbcl issue, sorry for not being clear enough!
("i suspect that the problem happens due to currupting sbcl's internal
state due to some missing locks in sbcl")
i just got this question when looking for the source of the problem.
but nevertheless i'm not sure how (setf (getf ...)) behaves with
multiple threads, especially when a new entry is added. after some
thoughts i think the worst corruption that would happen is duplicate
entries and deleted entries, so the current situation may not be too
bad at all.
but having a protected global cache for the created classes/prototypes
may be a good idea nevertheless, because it would probably speed
things up in a threaded environment. but again, i'm talking without
actually checking the code, so take it with a piece of salt...
--
attila
More information about the closer-devel
mailing list