Hi brent

Why do you change the defaultAction of the Warning class and not 
Deprecation?
Did I miss something?
By the way could we have a better contents for the debugger window?


Stef

!Warning methodsFor: 'exceptionDescription' stamp: 'brp 5/9/2003 12:54'!
defaultAction
	"The user should be notified of the occurrence of an exceptional 
occurrence and given an option of continuing or aborting the 
computation. The description of the occurrence should include any text 
specified as the argument of the #signal: message."

	Debugger
		openContext: thisContext
		label: 'Warning'
		contents: self messageText, '\\Select Proceed to continue, or close 
this window to cancel the operation.' withCRs.
	self resume! !


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>