Issue 5003 in pharo: Unwind blocks should always be executed in owning process

Status: Accepted
Owner: ----
Labels: Type-Bug

New issue 5003 by renggli: Unwind blocks should always be executed in  
owning process
http://code.google.com/p/pharo/issues/detail?id=5003

Terminating a process from the outside executes its unwind blocks  
(#ensure:, #ifCurtailed) in the process that initiates the termination, not  
in the owning process.


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

Updates:
        Cc: [hidden email]
        Labels: Milestone-1.4

Comment #1 on issue 5003 by [hidden email]: Unwind blocks should  
always be executed in owning process
http://code.google.com/p/pharo/issues/detail?id=5003

Igor. I want that we talk about that on a black board. I'm stupid, dull and  
naive with concurrency so the perfect guy to talk with you about that :)


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

Comment #2 on issue 5003 by [hidden email]: Unwind blocks should  
always be executed in owning process
http://code.google.com/p/pharo/issues/detail?id=5003

Igor? Can you think about that?


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