On 31 Aug 2015, at 10:18, Peter Uhn��k <i.uhnak@gmail.com> wrote:

On Mon, Aug 31, 2015 at 8:41 AM, stepharo <stepharo@free.fr> wrote:
But the tool of mark is a ui tool so why would you want to get a tool to define a rule in your case?

You can use the UI to create the rule, but the application of the rule can be scripted.
 
Yes, it would be nice to have a tool for creating the rules. But then, one can use Mark���s tool as is
for this already now for creating the rewrite rule and then copy-and-paste it.
An integration could make that even easier, but for me this is good enough for now.

RewriteTool creates classes with the rules, so I don't see the need for copy-pasting.
Why not just

self deprecated: anExplanationString rule: aRuleClassGeneratedByRewriteTool


good idea, this way the rule is reusable for a code critique rule (for those cases where it
makes sense, e.g. for ifNotNil: yes, as it is likely unique, but for #at: on SmalltalkImage, no ;-)

Marcus