On Wednesday, September 17, 2003, at 12:21 AM, Doug Way wrote:

> On Tuesday, September 16, 2003, at 06:48 PM, Avi Bryant wrote:
>
>> On Tue, 16 Sep 2003, Doug Way wrote:
>>
>>> I'm just concerned that if there are no warnings at all, package
>>> developers might not even notice that methods they rely on have been
>>> deprecated.  Perhaps this isn't a big problem in practice, I'm not 
>>> sure.
>>
>> I think that package developers just need to get into the habit of 
>> turning
>> #showDeprecationWarnings on as part of the process of checking for
>> compatibility with a new release of Squeak.  I don't think it's 
>> necessary
>> to be constantly informed that you're using a deprecated methods - 
>> just
>> that you be able to easily catch such uses during the release 
>> process. So
>> the preference seems right to me.
>
> Fair enough.
>
> Ok, I'll include this for 3.6.  Actually, I checked the changeset and 
> you left out the implementation for deprecationExplanation:, so here's 
> version 2 which includes that.  Also, I put it in the "debug" 
> preferences category rather than the overstuffed "general" category, 
> since it is somewhat related to debugging... let me know if there are 
> any violent objections to that.
>
> An extra review of my version 2 changeset would be welcome.  Although 
> we need to get the candidate gamma images out there, so assuming no 
> problems, I'll add this as an update tomorrow, and then create the 
> candidate images sometime tomorrow.
>
> - Doug
>
> <DeprecationPreference-avi.1.cs.gz>