2 Comments regarding restarts in the CL Condition system
- From: Madhu <enometh@xxxxxxxx>
- Date: Fri, 26 Jan 2007 10:13:37 +0530
Helu, I'd like to pose the following two points that I understand of
the condition system --
1. The restart function (i.e. the code executed when the restart is
invoked) does not have access to the condition object that
triggered it. (The condition object which is available to the
:test function supplied in RESTART-CASE, for example)
2. The interfaces to specifying restarts are all
macros. (WITH-SIMPLE-RESTART, RESTART-BIND, RESTART-CASE, and
possibly WITH-CONDITION-RESTARTS)
Re (1), it would seem desirable to have the condition object made
available to the restart code when invoked. (2) means there is no
functional interface (i.e. via functions) to specifying restarts
objects, and this would seem to imply one cannot programatically
create "condtion-handling-environments" at runtime --- without
recourse to EVAL or a bulky compile. (I suspect This issue is similar
to TRACE being a macro.)
It appears both (1) and (2) are related, and are artifacts of
`implementing' properties desired in the restart objects: that they
can be passed around and invoked.
Could a future design, in theory, remove both limitations (if i may
call them limitations), or is there any basic reason why (1) and (2)
should be this way?
--
Madhu
.
- Follow-Ups:
- Re: 2 Comments regarding restarts in the CL Condition system
- From: Barry Margolin
- Re: 2 Comments regarding restarts in the CL Condition system
- From: Kaz Kylheku
- Re: 2 Comments regarding restarts in the CL Condition system
- Prev by Date: Re: Is CMUCL insane? P.S. Me vs. CLM (Common Lisp Music)
- Next by Date: Re: 2 Comments regarding restarts in the CL Condition system
- Previous by thread: Is CMUCL insane? P.S. Me vs. CLM (Common Lisp Music)
- Next by thread: Re: 2 Comments regarding restarts in the CL Condition system
- Index(es):
Relevant Pages
|