Mariano Martinez Peck wrote: > > grrr shorcuts.. then I found AutomaticMethodCategorizerApplier which I > don't > care. > And I don't care if I need to close and open again the TestRunner. > > So....what I mean is that class creation notification increases Fuel > classes > materialization like 50%. Do you think this is un-important enough to > provide a way to NOT notify? I mean, should I provide a way to avoid that > and avoid the 50% ? or it will be totally unsafe? > > Thanks! > Yes, it will be totally unsafe, if tools hold caches relying on the notifications for invalidation (which is entirely appropriate). A better solution would be to provide bulk notifications, so instead of sending a notification to subscribers once for each class added, you update them only once, after all classes are created. Same holds true for other kind of system changes.
Cheers, Henry -- View this message in context: http://forum.world.st/Class-creation-notification-tp3837570p3841078.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
