Hi brent

I started to use your changeset and I was thinking that it would be 
good to have an extra argument to be able to
provide more information to the user. I removed the deprecated and 
replaced them by deprecatedExplanation: and deprecated: aBlock 
explanation: . I rmoved the imsple one because I want to force the user 
of deprecated to explain
why the method is deprecated or what to do. The client of the method 
deserves that.

You can have a look at the KCP-63 on 
http://minnow.cc.gatech.edu/squeak/3083

Stef


On Friday, May 9, 2003, at 04:14 PM, Brent Pinkney wrote:

> Change set attached, sorry.
>
> Hi,
>
> This is my second implemetation of the Deprecation warning.
>
>> From Deprecation's class comments...
>
> This Warning is signalled by methods which are deprecated.
>
> The use of Object>>#deprecated and Object>>#deprecated: aBlock is 
> recommended.
> e.g.
>
> Foo>>#oldMethod
> 	self deprecated.
>
> or
> Foo>>#oldMethod
> 	self deprecated: [ Bar>>#newMethod ].
>
>
> How does this get into 3.6alpha and become Standard Practice ?
>
> Thanks
>
> Brent
>
> <Deprecation.4.cs>