home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!cs.utexas.edu!zaphod.mps.ohio-state.edu!swrinde!mips!think.com!barmar
- From: barmar@think.com (Barry Margolin)
- Newsgroups: comp.lang.lisp
- Subject: Re: need some help with conditions and CLIM
- Message-ID: <171n9mINNe9u@early-bird.think.com>
- Date: 21 Aug 92 03:18:14 GMT
- References: <CHYDE.92Aug20142411@pecos.ads.com>
- Distribution: comp
- Organization: Thinking Machines Corporation, Cambridge MA, USA
- Lines: 29
- NNTP-Posting-Host: gandalf.think.com
-
- In article <CHYDE.92Aug20142411@pecos.ads.com> chyde@pecos.ads.com (Clinton Hyde) writes:
- >at the moment, I'm getting a ABORT or some sort signalled out of
- >CLIM's accepting-values, but if I use handler-case to try to grab it,
- >I seem to have the wrong name or something. so what I need today is to
- >know what gets signalled when I click on the <abort> exit-box. for the
- >future I'd like to know how to find ANYTHING that's signalled.
-
- If it's done correctly, aborting should be implemented by invoking a
- restart, not by signalling a condition. If you want to establish a handler
- for this, you can use WITH-SIMPLE-RESTART or RESTART-CASE, specifying the
- restart named ABORT.
-
- You'll have to do this inside the ACCEPTING-VALUES, since ACCEPTING-VALUES
- presumably sets up its own ABORT restart, and the innermost one is the one
- that will be invoked.
-
- It's also possible that ACCEPTING-VALUES is using some other mechanism to
- implement the exit boxes. It could just be doing a RETURN-FROM.
-
- I don't know of a way to find out what restarts or other exit mechanisms
- are being invoked, the way you can for conditions being signalled. And if
- it's using a lexical mechanism like GO or RETURN-FROM, there's no way for
- you to intercept it even if you do find out.
-
- --
- Barry Margolin
- System Manager, Thinking Machines Corp.
-
- barmar@think.com {uunet,harvard}!think!barmar
-