[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: catch-cancel
- To: reti@cambridge.apple.com (Kalman Reti), alice@digitool.com (Alice Hartley), korcuska@ils.nwu.edu (Michael Korcuska), info-mcl@digitool.com
- Subject: Re: catch-cancel
- From: reti@cambridge.apple.com (Kalman Reti)
- Date: Mon, 5 Jun 1995 11:07:38 -0500
- Sender: owner-info-mcl@digitool.com
At 9:58 6/5/95, Kalman Reti wrote:
>At 18:49 6/3/95, Alice Hartley wrote:
>>At 4:55 PM 5/31/95, Michael Korcuska wrote:
>>>In article <gclements-3105951036250001@mac21_58.keps.com>,
>>>gclements@keps.com (Geoffrey Clements) wrote:
[stuff removed]
>>>
>>
>>Yes its true that there is a (catch :cancel ...) withing the event processing
>>code. It should probably be mentioned somewhere in the documentation
>>that MCL uses the catch tag :cancel for some internal purposes.
>
>Maybe the catch tag should be something like the (this is from memory so
>I might not get it quite right) Lispm tag: if-you-throw-to-this-you-deserve-to-lose.
Sorry, it was too early in the morning. That suggestion of mine doesn't
apply here, since it needs to catch the :CANCEL throws sprinkled liberally
throughout the existing code.
I've previously expressed the opinion that handling the cancel button on
dialogs by doing a throw to :cancel is just a bad idea. It should signal a
condition, just like anything else. This would allow the user to use a
global condition handler instead of a stack-based one which wouldn't be
applicable when the event is handled in another process.
>
>>
>>
>>Alice@digitool.com