freenode/#sbcl - IRC Chatlog
Search
10:48:16
luis
Shinmera: Krystof presented an idea at SBCL20 about being able to represent various NaN values. This is not something that current implementations (Lisp or otherwise) do.
11:35:59
man213
Hi guys. I need a help with sb-alien. Could somebody point me a way to define cross-referencing alien structs?
11:52:28
luis
man213: (sb-alien:define-alien-type nil (sb-alien:struct b (x (* (struct a))))) (sb-alien:define-alien-type nil (sb-alien:struct a (x (* (struct b)))))
12:07:06
man213
luis: Thank you very much, luis. You really helped. My mistake was that I referred pointer to a struct type as (* struct-type-name) and not as (* (struct struct-type-name)).
18:55:09
White_Flame
here's the annoying issue I've been having with some old code: https://pastebin.com/nwH1a7jR
19:12:47
White_Flame
I've been pondering changing *=>+ in the names, then having a symbol-macro converting *foo* to +foo+ to avoid those warning outputs, but is there a way to actually silence them? should muffle-warnings have prevented that output?
19:17:20
White_Flame
well, the warning was never reported as caught. This bare output went to stdout without any "caught STYLE-WARNING", and "compilatin finished in 0:00..." etc at the end with no report of warnings
19:17:38
White_Flame
so it seems like it was partially muffled, but the pritning still leaked out, which might be a bug if true?
19:18:09
Bike
"caught STYLE-WARNING" is from the compiler, i'm pretty sure. if you're just getting STYLE-WARNING maybe it's just a regular old warning