This approach of swapping out inactive classes have two big problems:
- The granularity is too high: the class. As soon as only one method is invoked, the whole class is recovered. - It is very common to recover all classes doing a simple action. For example, searching for implementors or senders of a certain method. Because of this, when you are developing in your Smalltalk image is very likely that all classes are recovered in less than 5 minutes of work. It is not useful. Browsing or editing code seems not to be a problem, thus. Maybe this approach has more sense in production images rather than development.
I guess the next tool you'll make is CUDMethodUseDiscover? ;)
:) I hope so ;) But it will be MUDMethodUseDiscover hahahaha
Good job, and good luck!
Cheers, Henry
PS. like in MessageTally, maybe a useful constructor method would be one taking a block as argument, and running trace during its execution?
Thanks Henrik for the excellent suggestion. Committed in ClassesUseDiscover-MarianoMartinezPeck.33 Now you can do for example: aDiscoverer := CUDClassesUseDiscoverer discoverOn: [Transcript show: 'testDiscoveryOnBlocks']. aDiscoverer activeClassesDuringDiscovery Or aDiscoverer := CUDClassesUseDiscoverer discoverWithTraceOn: [Transcript show: 'testDiscoveryOnBlocks']. aDiscoverer activeClassesDuringDiscovery :)
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project