4 ms·
CL's default behavior drops you into the debugger. That can be customized in delivered applications to do whatever you want. I sell binary-only command-line CL
by zachbeane 17y ago
CL's default behavior drops you into the debugger. That can be customized in delivered applications to do whatever you want. I sell binary-only command-line CL applications to non-technical users and they don't need to know that Lisp's behind it at all.
- pw0ncakes 17y agoInteresting. How hard is this to do? I don't know much about CL.
- lispm 17y agoWrap something like this around a main startup function for your application: (handler-case (main-user-function) (error (c) (princ "a serious error, I'm quitting") (quit)) (condition (c) (princ "we have a problem") (when (y-or-n-p "abort?") (abort)))) It handles conditions of class ERROR in the first clause and conditions of class condition (all kinds of stuff that one can signal) in the second clause. The variable 'c' would be the condition object. You could inspect it and print more useful help, show dialogs, look for restarts and more.