[Pharo-project] Proposal to refactor MethodFinder with pragmas

Pavel Krivanek pavel.krivanek at gmail.com
Fri Jun 24 05:34:22 EDT 2011


What about only to use a pragma directly in the methods that will
inform that the method has no side effect and doesn't modify the state
of the object? This information may be used not only for the
MethodFinder.

-- Pavel

On Fri, Jun 24, 2011 at 11:25 AM, Damien Cassou <damien.cassou at gmail.com> wrote:
> Currently MethodFinder uses a list of acceptable selectors to execute.
> This list of selectors is not maintained which results in a lot of
> selectors to exist only in this list as they have been removed in the
> system. I propose to use pragmas on classes to generate this list
> automatically.
>
> Here is an example
>
> Magnitude class>>finderApprovedMethods
>       <finderApproveInstanceMethod: #max:>
>       <finderApproveInstanceMethod: #min:>
>       <finderApproveInstanceMethod: #min:max:>
>       <finderApproveInstanceMethod: #< >
>       <finderApproveInstanceMethod: #<= >
>       <finderApproveInstanceMethod: #< >
>       <finderApproveInstanceMethod: #<= >
>       <finderApproveInstanceMethod: #between:and: >
>
> What do you think?
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Lambdas are relegated to relative obscurity until Java makes them
> popular by not having them." James Iry
>
>




More information about the Pharo-dev mailing list