ok....For those who were not here hahaha. We have just talked with Stef. There is no problem because AutomaticMethodCategorizer ONLY takes into account the methods that are not yet categorized. Thus....if you have *Something it means it is already categorized...thus, it does nothing.
Is it ok? Mariano On Tue, Aug 17, 2010 at 10:08 AM, Stéphane Ducasse < [email protected]> wrote: > > This is not up to AutomaticMethodCategorizer. > > yes it is. > The automaticCategorizer should not when it get applied to a class breaks > packages > > > I mean, by code, the only defined rules are the ones that are in > #defaultCategorizationRules > > If you want you can add more rules. For a rule you can say something like > this: > > > > add: (MethodCategorizationRule whenSelectorMatches: 'is*' categorizeIn: > #testing); > > > > if you do something like this for example: > > > > add: (MethodCategorizationRule whenSelectorMatches: 'is*' categorizeIn: > #*Something); > > > > There will be no error in AutomaticMethodCategorizer and Something will > be recognized as it were a package. > > > > More or less could happen the same with a selector that doesn't apply to > any rule. For example, suppose #aFunnySelector doesn't match any rule, but > there are 10 implementors in the image and the 80% of them has category > *Something. Then. it will apply *Something also to that selector. > > > > That's what I understood. However, I don't think it is a big deal and we > can live with that. > > No! > Automatic categorizer should be able to be applied system wide and not > break all the packages. > > Stef > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
