I wonder if it was a bad idea if the CL code behind slime-interrupt first tried to signal the implementation's native interrupt condition so people have a chance to do
(handler-case (loop) (sb-sys:interactive-interrupt () (print-stats)))
-T.
* Tobias C Rittweiler [2010-12-15 11:07] writes:
I wonder if it was a bad idea if the CL code behind slime-interrupt first tried to signal the implementation's native interrupt condition so people have a chance to do
(handler-case (loop) (sb-sys:interactive-interrupt () (print-stats)))
Perhaps not a bad idea, but probably not a good one either. Firstly, it doesn't sound like often needed feature. Secondly, a "native interrupt condition" doesn't exist in all implementations; more likely we would create our own condition. Finally, interrupt handling is complicated enough and I think we should keep third party code out of the path whenever possible.
Helmut