Lukas Renggli wrote:
>
> Note that the classes contain actually excellent documentation.
>
Do you have any particular one in mind? I traced OB's execution to
RBStringReplaceRule and then looked up the hierarchy finding basic
few-sentence descriptions, but nothing in-depth about how to search and
replace.
Lukas Renggli wrote:
>
> Actually you can do it with a few clicks: Select #deprecated:, click
> on "Refactor method > Add parameter" and follow the instructions.
>
Notice I asked about the API, not about the OB GUI. I needed to
programmatically change each one depending on the sender's timeStamp and the
collections of what was deprecated in which version. Also, there are already
methods in the system with the name I'm changing to, so OB just mentions
that and fails.
Let me ask maybe a better question - how would you do the following
programmatically?
For each method that sends #deprecated: (except for certain excluded ones)
change the send to #deprecated:on:in:
where the second argument is the calling method's timeStamp
and the third is 'Pharo1.3' or 'Pharo1.4' depending on which pre-made
list it appears on.
Cheers,
Sean
--
View this message in context:
http://forum.world.st/RB-API-tp3781019p3781179.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
