[Pharo-project] Bug in ThreadSafeTranscript
Hi: ThreadSafeTranscript crShow: is not thread-safe, but definitely need to be thread-safe. The problem is, it is using a mutex currently. (I guess thats the reason why there is no accessSemaphore critical: [...]. in crShow) Replacing it by a reentrant/recursive Monitor would probably allow to avoid code duplication. Best Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525
stefan send code :) Stef On Jan 20, 2010, at 9:27 PM, Stefan Marr wrote:
Hi:
ThreadSafeTranscript crShow: is not thread-safe, but definitely need to be thread-safe.
The problem is, it is using a mutex currently. (I guess thats the reason why there is no accessSemaphore critical: [...]. in crShow)
Replacing it by a reentrant/recursive Monitor would probably allow to avoid code duplication.
Best Stefan
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
participants (2)
-
Stefan Marr -
Stéphane Ducasse