>> We are focusing on other stuff right now. I got a look at VisualWorks
>> and
>> they are inconsistent in naming Error. So if other like the idea go
>> ahead but think that we should have a deprecation mechanism for them.
>> For method this is easy but for class renaming it does not work.
>> May be one idea would be to inspect the stack when a changeset is
>> loaded and have a table somewhere containing the renaming information
>> DivideByZeroError -> DivideByZero.
>
> Not sure how to do the deprecation itself, but to provide a transition
> phase one can use subclassing.  Make DivideByZero be a subclass of
> DivideByZeroError.

Yes I never thought of that and this is a good way to do it. I had a 
lot of problem
with renaming class in our environment here because this was not easy 
to deprecate them simply.
But I really like this idea.