+ 1 We should improve the base system. So if you have suggestion or needs please let us know.
implements Object>>announce: , meaning that classes that want to
âannounceâ , can simply reimplement #subscriptionRegistryOrNil , while in Pharo you need to inherit from Annoucer or reimplement all its methods.
Does anyone know why there are differences between the two dialects? Is Pharo not keept up to date in this area?
It was a conscious choice. Initially, announcements which were added to pharo has very compact implementation, with minimal features available. It was inspired by Announcements from VisualWorks, but implemented from scratch based only on publicly available description. I guess it was done specifically to avoid potential problems with licensing. Lukas could say more about it, since it is he, who did an initial implementation , if i'm not mistaken.
If you think there is a missing functionality, which could be useful for general use, feel free to propose the changes (but please do that in pharo-dev list), so we will discuss it and consider for inclusion in next Pharo release.
Kind regards Runar
-- Best regards, Igor Stasenko AKA sig.