Hello,
I think #executeMethod was a shortcut for method without arguments of the
method #withArgs:executeMethod:. I missed it too, so I guess you can add a
bug report, create and commit a slice and lastly it will be integrated in
Pharo in the next few days.
#withArgs:executeMethod: is implemented in ProtoObject, but we take care
not to have too many methods there. This kind of facilities are usually in
Object (For example, #isNil is in ProtoObject, but #notNil which is a
facility for 'isNil not' is in Object). So I guess what you miss is:
Object>>*executeMethod*: method
^ self withArgs: #( ) executeMethod: method
Best,
2013/10/26 Charles Hixson <charleshi...@earthlink.net>
> I'm using:
>
> Pharo2.0
> Latest update: #20625
>
> I'm at "Reflection continued
>
> When I do the command to go to the next lesson:
> ProfStef default executeMethod: (ProfStef lookupSelector:#next).
>
> I get the error:
> ProfStef(Object) doesNotUnderstand: #executeMethod
>
> When I browse to the class in the system browser, ProfStef doesn't have an
> executeMethod object.
> I also checked Object and ProtoObject,just to be sure, but neither of them
> listed an executeMethod either.
>
> P.S.: I also looked at the Class Methods, though default looks like it
> returns an instance, so that didn't feel reasonable.
>
> Where is executeMethod supposed to reside, and was this an intentional
> change that just hasn't propagated yet ('m guessing the removal of the
> method) or is something wrong with my image? Also, if I wanted to include
> it into ProfStef, what would the method look like?
>
> --
> Charles Hixson
>
>
>
