2009/3/29 Stéphane Ducasse <[email protected]>: > did you check what the semaphore critical section is protecting? > cr, tab, nextPutAll: and more and not protected. > > then transcriptStream inherits from stream which is not threadsafe, so > everything can happen. > I think that having a real thread safe output is a must. >
as well as thread-safe updating. Btw, take a look at the http://bugs.squeak.org/view.php?id=7033 The way how Transcript window updates itself is not safe. It should use deferUIMessage to update itself using regular world cycle. > Stef > > On Mar 29, 2009, at 5:55 PM, Keith Hodges wrote: > >> Stéphane Ducasse wrote: >>> Hi >>> >>> I would really like that we get a threadSafeTranscript so I coded >>> one. >>> If you can comment this would help me. >>> >>> Stef >> What is the difference tot he exisitng one, it has an access >> semaphore too. >> >> Keith >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
