Now what we should do is probably to get a more dynamic way to tag methods because not methodFinder has a huge baglog of selectors and it is probably not in sync with the system
We were thinking about using pragma to tag methods that should not be executed but we need a proof of concept. Stef On Aug 27, 2010, at 8:59 PM, Bart Gauquie wrote: > Dear list, > > I was showing off Pharo to a colleague today and was surprised that. > > My quick introduction of adding new methods on existing system classes > > String>>firstLetter > ^self copyFrom: 1 to: 1 > > - extension on String worked immediately. But that: > > in the MethodFinder evaluating: 'tried'.'t' > did not return my method I just added .... :-( > > Turns out that MethodFinder has a class side Set of Approved and AddAndRemove > methods. > What is the rationale of this? Should we not allow any method, but exclude > some tricky ones (doesNotUnderstand:, ... )? > > Kind Regards, > > Bart > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
