On Aug 3, 2010, at 2:12 PM, Alexandre Bergel wrote: >> alex my question was more naive and probably it shows that I do not know how >> the announce protocol should be implemented >> but why do you have to record them? > > The purpose of an announcer is to dispatch events. Callbacks are registered > in an announcer, and an announcer receives and dispatch events to the > callbacks. > In my enh, each unit test (subclass of TestCase) has an announcer. Maybe this > is not a good strategy. Having one global announcer for unit test may be more > convenient in some situations. > > Something nice, is that if there is no callback registered, events are not > emitted. This means that this should incur no overhead (even though I did not > measured).
Thanks for the explanation so I think that then this is better to have one per class this way we do not have the Dependent kind of problems where you have plenty of objects registering to a single table and get everytbody slow. Stef > > Cheers, > Alexandre > > > >> >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project@lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project@lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project