Issue 4296 in pharo: Strange behavior with announcements

Status: Accepted
Owner: [hidden email]

New issue 4296 by [hidden email]: Strange behavior with announcements
http://code.google.com/p/pharo/issues/detail?id=4296

Today I experimented some strange behaviours with announcements that I  
didn't have in some previous moose images (moose in now based on Pharo 1.3).
I think that there was some changes related to announcements in pharo  
recently, but I could not be sure it is related.

At one point in my code I have:

browser on: AnnouncementClass send: #actionSelector
browser announce: anAnnouncementClass.
....
....

The behaviour I have is like if #actionSelector was executed asynchronously  
from the rest of the code below 'browser announce: ...' .
Not sure but there is maybe something with exception signals. If any signal  
is emited in #actionSelector it will not execute the rest of the method.

I was at least able to write a test that do not pass in latest pharo 1.3  
(#13218)

Gofer new
        squeaksource: 'DelaunayTmpStuffs';
        package: 'ExampleAnnouncementProblems';
        load.




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

Updates:
        Labels: Milestone-1.3

Comment #1 on issue 4296 by [hidden email]: Strange behavior with  
announcements
http://code.google.com/p/pharo/issues/detail?id=4296

(No comment was entered for this change.)


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

Updates:
        Labels: Type-Bug

Comment #2 on issue 4296 by [hidden email]: Strange behavior with  
announcements
http://code.google.com/p/pharo/issues/detail?id=4296

(No comment was entered for this change.)


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

Updates:
        Status: Invalid

Comment #3 on issue 4296 by [hidden email]: Strange behavior with  
announcements
http://code.google.com/p/pharo/issues/detail?id=4296

This issue is invalid. As i explained to Cyrille,
one should not signal an exception(s) in announcement handling code and  
expect that
it will be handled by some code which announced the event.
Because the it will mean that you can prevent announcer to deliver announce  
to other subscribers.
That's why there is #on:fork: which guarantees that announcement will be  
delivered to all subscribers. And those who signaling unhandled exceptions,  
they will be forked into separate process. So, this is intended feature and  
not a bug.


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