[Openmcl-devel] Is this an OpenMCL 'problem'?

Phil pbpublist at comcast.net
Fri Apr 7 20:30:57 UTC 2006

Gary Byers wrote:

> I don't think that either of these approaches is entirely optimal.  I
> think that I'd ultimately favor a mixture of the two: dropping into
> the kernel debugger first, but providing an option to attempt to recover
> by treating the exception as a lisp error.

I appreciate the detail on the options and rationale and it makes sense 
how and why it's being handled the way it is.  From a development 
standpoint, it would be nice if Slime handled the situation better (OT 
for this list so I'll take it over to slime).  From a deployment 
standpoint, does this approach preclude a graceful exit of an app? (i.e. 
at least log the error and present the user with an error dialog before 

> ccl:examples;cocoa-backtrace.lisp uses NSOutlineViews and actually
> doesn't do anything too complicated with them, but the rest of it
> (dealing with "stack frame objects") is pretty obscure ...

I'll take a look at that code and, if I still can't get it going, start 
a new thread with specifics.


More information about the Openmcl-devel mailing list