Michael Rueger wrote: > Keith Hodges wrote: > >>> We will include it. >>> >>> >>> Thanks, we will try with Pharo then. >>> Lautaro Fernández >> I am confused. Surely you would expect a loadable package to remain >> loadable and only be called up if needed? > > Although I'm normally the first to argue against including more stuff > into the core image I think Announcements need to be part of core. > This will allow us to have *one* mechanism for signaling/subscribing and > can over time replace the different variants that are now used and > provide a solid base for anyone needing such a mechanism. > In the experimental forks I have worked on having Announcements > available made all the difference. >
+1 We need to standarize to only one implementation, if posible, adding the features needed from the others if neccesary. It could be that some features from other implementation could not be integrated because of architectural reason, but that will be discussed when the time arrives. Miguel Cobá > Michael > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
