Anthony,

Yes, this makes a lot of sense - I'd actually vote for a [CLEANUP]
submission or somesuch just for this change as it has been biting me (and
probably others) regularly too. BTW, if you're just at it, you might also
remove some of the other old EH handling nonsense which nobody uses any
longer ;-)

Cheers,
  - Andreas

> -----Original Message-----
> From: squeak-dev-bounces at lists.squeakfoundation.org 
> [mailto:squeak-dev-bounces at lists.squeakfoundation.org] On 
> Behalf Of Anthony Hannan
> Sent: Thursday, March 27, 2003 3:55 PM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: RE: Debugger woes
> 
> 
> "Andreas Raab" <andreas.raab at gmx.de> wrote:
> > Actually, #valueUninterruptably is legacy code for VMs which don't
> > have the proper unwind support. Therefore, you can safely remove
> > any sends of #valueUninterruptably and replace them by #value
> 
> The closure compiler runtime implements valueUninterruptably 
> (and ifCurtailed)
> as:
> 
> valueUninterruptably
> 	"Temporarily make my home Context unable to return 
> control to its sender, to
> guard against circumlocution of the ensured behavior."
> 
> 	^ self ifCurtailed: [^ self]
> 
> 
> ifCurtailed: aBlock
> 	"Evaluate the receiver with an abnormal termination action."
> 
> 	<primitive: 198>
> 	^ self value
> 
> 
> Cheers,
> Anthony
> 
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
> http://platinum.yahoo.com
>