home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!convex!darwin.sura.net!mips!swrinde!elroy.jpl.nasa.gov!ames!agate!stanford.edu!lucid.com!karoshi!york
- From: york@oakland-hills.lucid.com (Bill York)
- Newsgroups: comp.lang.lisp
- Subject: Re: need some help with conditions and CLIM
- Message-ID: <YORK.92Aug20135351@oakland-hills.lucid.com>
- Date: 20 Aug 92 18:53:51 GMT
- References: <CHYDE.92Aug20142411@pecos.ads.com>
- Sender: usenet@lucid.com
- Reply-To: York@Lucid.COM
- Distribution: comp
- Organization: Lucid, Inc.
- Lines: 13
- In-Reply-To: chyde@pecos.ads.com's message of Thu, 20 Aug 1992 19:24:11 GMT
-
- In article <CHYDE.92Aug20142411@pecos.ads.com> chyde@pecos.ads.com (Clinton Hyde) writes:
-
- From: chyde@pecos.ads.com (Clinton Hyde)
-
- anyway, I would like to know how (if it's possible) to find out
- programmatically (or is that automagically) what condition is
- signalled when some piece of code does so.
-
- You could try wrapping the following around the offending code
- (represented here is "(/ 3 0)").
-
- (handler-case (/ 3 0)
- (error (e) (format t "~&The condition ~S was signalled" e)))
-