freenode/lisp - IRC Chatlog
Search
17:02:52
Josh_2
Is the mailman service working for common-lisp.net? I have subbed to a mailing list but not received my confirmation
18:34:45
Xach
the project isn't dead-dead but the PR to fix the UB is a few weeks old with no remarks. in cl-land that's not bad but i really would like a nice version in time for the end of august.
21:50:55
sveit
I am confused how condition tests are supposed to work. Why is it that with custom condition types, '(nil) is always passed as the condition to the test? A simple failing example is: https://pastebin.com/QE87KacT
21:54:04
sveit
phoe: i was just copying the error i get from sbcl when I run the example in my pastebin (which just defines an custom condition and a conditional restart). More precisely, sbcl complains "no applicable method for generic function test-slot when called with arguments (NIL)"
21:55:09
Bike
also, p hoe is right: test functions should be prepared to accept nil, and also any condition object.
21:55:12
phoe
if COMPUTE-RESTARTS is called without a condition object, then restart test functions will be called with NIL
21:55:41
phoe
if they're called with a condition object - then that argument will be that condition boject
21:56:38
sveit
ah, thanks. didn't see that in the hyperspec. seems like a strange convention, isn't compute-restarts in the usual case called without a condition object?
21:57:36
phoe
the debugger is allowed (and should) call COMPUTE-RESTARTS *with* a condition object, in particular, with the condition object that the debugger has been entered with
21:58:13
phoe
it's not really specified in the spec (as the debugger isn't really specified), but it's the only logical behavior
21:58:43
sveit
hmm. Doesn't seem to be the behaviour in my SBCL (that error I get was from interactively calling (test-function) in REPL)
21:58:46
phoe
users are also allowed to do the same, e.g. if they end up in the debugger REPL and want to resolve the situation manually via calling FIND-RESTART and INVOKE-RESTART and what else