Re: handler-bind / handler-case
- From: "WoodHacker" <RamsayW@xxxxxxxxxxx>
- Date: 8 Oct 2005 05:56:25 -0700
I still can't get this to work and I'm more confused than ever.
Clearly, I have no idea what I'm doing. If I use the following code
(handler-bind ((error '(missing-font-error font-name))
(setf font (xlib:open-font *display*
font-name)))
and use a font that I know exists, the font is loaded. However, if I
put in a bogus font I get a runtime type error. It tells me
"missing-font-error" is not a function. If I remove the quote it
gives me the proper error. However, in this case it ALWAYS gives me
the error even when the font is openable. Shouldn't it be working
this way: handler-bind checks the form. If the form fails it looks at
it's error list - in this case any error will do - and calls the
function listed for that error? All I want to do is trap the
condition where a font can't be opened and tell the user which font
can't be opened - for whatever reason. The error you get from SBCL
for an open-font failure is incomprehensable to the average user.
.
- Follow-Ups:
- Re: handler-bind / handler-case
- From: Alan Crowe
- Re: handler-bind / handler-case
- From: Rainer Joswig
- Re: handler-bind / handler-case
- References:
- handler-bind / handler-case
- From: WoodHacker
- Re: handler-bind / handler-case
- From: Jeff M.
- Re: handler-bind / handler-case
- From: WoodHacker
- Re: handler-bind / handler-case
- From: Barry Margolin
- handler-bind / handler-case
- Prev by Date: Re: What's so great about lisp?
- Next by Date: Re: What's so great about lisp?
- Previous by thread: Re: handler-bind / handler-case
- Next by thread: Re: handler-bind / handler-case
- Index(es):
Relevant Pages
|