I don't see why it matters.  If developers don't put in the effort 
they'll quickly learn once the methods get removed that they need to 
check these things during the previous release.  I don't think we need 
to hand-hold developers too much, particularly at the expense of 
usability for other users.  We don't need to force developers to deal 
with deprecation early, we just need to make it easy for them to do so 
and provide incentive (their software won't suddenly cease to work).

But I think I'm more convinced by Avi's preference idea now than I was 
before anyway... it's nice to have the context when you actually go to 
solve the issue.

Julian

Roel Wuyts wrote:
> The fact that most users do not have their transcript open mean that a 
> lot won't even see this.
> 
> Could we do something like in VW: instead of popping up a regular 
> unhandled exception, pop-up a window that contains a number of options:
> 1- debug (as now)
> 2- proceed once (so only this once, next occurence will pop-up again)
> 3- proceed all (no more windows for deprecated methods; Transcript 
> instead).
> 
> 
> Note that, if it is annoying to end-users who do not dare to change it 
> themselves, they might start complaining on the list, putting peer 
> pressures on the developers of those packages to fix them :-)
> 
> On Tuesday, Sep 16, 2003, at 20:43 Europe/Zurich, Adam Spitz wrote:
> 
>> ducasse <ducasse at iam.unibe.ch> wrote:
>>
>>> I agree so propose something.
>>
>>
>> Julian proposed spitting out a Transcript message instead of popping up
>> the dialog box. Sounds reasonable to me.
>>
>>
>> Adam
>>
>>
> Roel Wuyts                                                   Software 
> Composition Group
> roel.wuyts at iam.unibe.ch                       University of Bern, 
> Switzerland
> http://www.iam.unibe.ch/~wuyts/
> Board Member of the European Smalltalk User Group: www.esug.org
> 
>