Hani
what would be good is: add a preference to the importingContext so that we can control if we want to get referencing classes
this way we should be able to write Importer new importingContext extractReferencingClasses ....
then write one or two tests that you put in the importer tests.
stef
On 21 déc. 07, at 12:29, Hani ABDEEN wrote:
this has been proposed by Reinout Heeck:
mc := MethodCollector new. bindingToSearch := OrderedCollection fullyQualifiedReference binding. filter := mc referencesTo: bindingToSearch. result := mc select: filter.
and it work very well.
Now the question for moose developers is: do you have an opposite idea about the modification of SmaltalkImporter. Note that, in moose, smalltalk models will be bigger than before.
bests, Hani
On Dec 21, 2007, at 11:50 AM, Adrian Kuhn wrote:
On 21 Dec 2007, at 9:02 , Stéphane Ducasse wrote:
However, Smalltalk's senders of yields tons of false positives. In RBCrawler, what I do is a type inference at byte code level to get better data.
We want just class references for now.
Oops, I misunderstood senders-of.
Well it should be very straight forward to write a MethodCollector that collects references to classes: references to classes are stored in the literal array of compiled methods, as BindingReferences.
NB, I have a custom collector somewhere in CodeFoo or VisualWorksFoo.
cheers, AA
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev