Updates: Labels: Component-SmalltalkImporter
Comment #4 on issue 435 by tudor.gi...@gmail.com: Using RoelTyper for a better precision of method invocation http://code.google.com/p/moose-technology/issues/detail?id=435
It seems that RoelTyper does not work for all classes. Try this code for getting the classes that raise an error:
classes := Dictionary new. Object withAllSubclassesDo: [:each | [(TypeCollector typeInstvarsOfClass: each )] on: Error do: [:error | classes at: each put: error ]]. classes inspect
Comment #5 on issue 435 by tudor.gi...@gmail.com: Using RoelTyper for a better precision of method invocation http://code.google.com/p/moose-technology/issues/detail?id=435
In Moose 4.7, it seems that only ColoredDSM is affected by this. It would be great if someone would take a look at this.
Comment #6 on issue 435 by jannik.l...@gmail.com: Using RoelTyper for a better precision of method invocation http://code.google.com/p/moose-technology/issues/detail?id=435
Ok, I will take a look.
Comment #7 on issue 435 by jannik.l...@gmail.com: Using RoelTyper for a better precision of method invocation http://code.google.com/p/moose-technology/issues/detail?id=435
I do not understand what is the problem.
Comment #8 on issue 435 by tudor.gi...@gmail.com: Using RoelTyper for a better precision of method invocation http://code.google.com/p/moose-technology/issues/detail?id=435
This is likely not a DSM problem, but a RoelTyper one :). It's just that it exhibits in the ColoredDSM class.
To reproduce just run this code in the latest Moose image.
classes := Dictionary new. Object withAllSubclassesDo: [:each | [(TypeCollector typeInstvarsOfClass: each )] on: Error do: [:error | classes at: each put: error ]]. classes inspect
You will get a list of all the classes for which RoelTyper throws an error. There used to be several of these, but somehow now we get only one.
Updates: Status: Fixed Labels: Milestone-5.0
Comment #9 on issue 435 by tu...@tudorgirba.com: Using RoelTyper for a better precision of method invocation http://code.google.com/p/moose-technology/issues/detail?id=435
This seems to not be a problem in Pharo 3.0 anymore.