Re: Issue 3428 in pharo: Semaphore Enh

Comment #5 on issue 3428 by [hidden email]: Semaphore Enh
http://code.google.com/p/pharo/issues/detail?id=3428

Issue 3231 has been merged into this issue.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #6 on issue 3428 by [hidden email]: Semaphore Enh
http://code.google.com/p/pharo/issues/detail?id=3428

Igor should have a look but it's fixed


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #8 on issue 3428 by [hidden email]: Semaphore Enh
http://code.google.com/p/pharo/issues/detail?id=3428

As i said before, i don't see much need in using #valueNoContextSwitch  
there..
I cannot make up a good example where just using #value create problems.

The reason is that during evaluation of provided block argument in  
waitIfLocked: ,
a semaphore can be signaled at any moment.. So, you cannot assume that  
semaphore will remain unsignaled during evaluation of the block, you can  
only assume that at the attempt of waiting for a signal it has no signals,  
and therefore ifLocked: branch evaluated instead.



_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker