On 09 Jul 2014, at 17:16, Camille Teruel <camille.teruel@gmail.com> wrote:
Hi Yuriy,
If I remember well, originally, there was #canUnderstand: that checked if a method with the given selector is present in the class hierarchy while #canPerform: was also checking that it is not a subclassResponsibility, an explicitRequirement or a shouldBeDefined method. Right now, both does the latter, I don't know why.
Maybe someone knows. Letâs wait a bit :)
I had trouble with this change because it broke some critics rules ("message sent but not implemented" for ex).
Yes, Iâve started to investigate https://pharo.fogbugz.com/f/cases/13521/RBMissingSubclassResponsibilityRule-... and found out that there is a problem with #canUnderstand: Uko
Camille
On 9 juil. 2014, at 16:50, Yuriy Tymchuk <yuriy.tymchuk@me.com> wrote:
Hi guys,
Iâm wandering if #canUnderstand: is implemented in a right way. I has exactly the same implementation as #canPerform:, so I wander if itâs a part of renaming process or one of the methods is not doing what they should.
Uko