Search
7:07:29
Nilby
type-of shouldn't return an integer right?
7:11:03
beach
Right, an integer is not a type specifier.
7:11:13
Nilby
also this shouldn't be true? https://plaster.tymoon.eu/view/3826#3826
7:14:51
beach
Where did this come up?
7:15:19
Nilby
it must be an implementation bug, but one that's probably my problem since i'm probably using internal debugging functions wrong
7:16:02
Nilby
It's in a debugger running on sbcl. Happens when I'm examining the stack.
7:18:44
Nilby
It's very difficult when there's simultaneously a bug in my program, the debugger, and errors in implementation print-object methods.
7:19:09
beach
I agree. Buggy tools make things very difficult.
8:39:36
Nilby
I wonder what it means when #<FUNCTION <<error printing object>> shows up sbcl's slime backtrace
8:40:56
hayley
It means the object couldn't be printed for some reason, so you get that text to have any backtrace at all.
8:41:20
beach
It looks like someone defined a method on PRINT-OBJECT that calls PRINT-UNREADABLE-OBJECT, but that method is buggy.
8:43:06
Nilby
Should I be concerned? Why wouldn't I be able to print something?
8:43:50
beach
If an error is signaled during printing, then the printing fails.