Esteban A. Maringolo wrote
>> That means with a code rewrite rule. Deprecations are not enough.
> Why not both?

It seems like you're both saying the same thing, no? Isn't this all
accomplished via:
                deprecated: 'Renamed to #action because now accepts any 
valuable as an
action (e.g. aBlock).'
                on: '10/24/2017'
                in: #Pharo61
                transformWith: '`@receiver selector' 
                                                -> '`@receiver action'.

Or are you saying there should be a collection of rewrite rules even after
the method is totally removed so one can bring a very old project up to the
newest APIs?

Sent from:

Reply via email to