On 2 January 2012 21:04, Lukas Renggli <[email protected]> wrote: >>> Now for me you don't need to change the semantics of the Pharo >>> Announcements again. Now for my code I will just use my own >>> implementation that has exactly the behavior and performance >>> characteristics I need. >> >> Lukas our state of mind is that we want the infrastructure gets better so we >> like to change >> for a better one if this better one is better. > > Seems that the understanding of what is better/worse and what is > progress/regress is rather different among people. > >> If everybody has its own version then we do not improve the infrastructure. > > Performance issues aside, the current implementation forces me to use > a different implementation because Pharo's announcements have a > different implementation of selecting the handler (point 7). However, > the really weird thing is that Pharo's announcements are now suddenly > inconsistent with the Pharo exceptions and how they select the > handler. Do you think this is better or worse? > you lost me here. why announcements have to be consistent with exceptions? something which is completely orthogonal to them? it is like saying that apples are inconsistent with oranges.
aside of that, i added the changeset, so you can now choose whether your announcement subscription is handling announcement or not based on announcement object itself, not its class. see http://code.google.com/p/pharo/issues/detail?id=5145 -- Best regards, Igor Stasenko.
