Comment #3 on issue 617 by cy.delau...(a)gmail.com: RPackage has a self halt http://code.google.com/p/moose-technology/issues/detail?id=617 It seems that even at the beginning, the organizer is not well initialized. If you just evaluate (Behavior >> #compilerClass) packageFromOrganizer: RPackageOrganizer default you have the halt

Comment #5 on issue 617 by cy.delau...(a)gmail.com: RPackage has a self halt http://code.google.com/p/moose-technology/issues/detail?id=617 I think I found where was coming from the problem, but I 'm not sure about the solution to give. Currently in RPackage, if a compiledMethod in a class is coming from a trait, we do not add it to the package of the class. The consequence is that such methods have no parent RPackage , which is wrong (and which is the problem , see (Behavior >> #compilerClass) packageFromOrganizer: RPackageOrganizer default). The reason I deal with such methods like that, is that PackageInfo >> methods does not return those methods, and then Monticello is expecting this behavior. Monticello needs to retrieve methods only coming from the class. The solutions I was thinking about are : - let RPackage not registering methods from traits but modify CompiledMethod >> packageFromOrganizer: to return the package of the trait - or modify RPackage to register those method. I guess we should add them in a new specific dictionary (classDefinedSelectorsFromTrait .. ). Then we would be able to filter them. The 'hard' work for this solution, would be to keep updated this dictionary (knowing that when we recompile a method coming from trait,it become a method from the class )

Updates: Status: Fixed Comment #7 on issue 617 by tudor.gi...(a)gmail.com: RPackage has a self halt http://code.google.com/p/moose-technology/issues/detail?id=617 (No comment was entered for this change.)