freenode/#sbcl - IRC Chatlog
Search
11:46:21
pkhuong
if your comparator is so simple that you care about that, the binary search loop shouldn't branch on =
13:34:16
TeMPOraL
hi all, a question; I'm digging into SBCL's implementation of trace, trying to convert it to generate traces into a data structure (for use in situations where *trace-output* may be written to by something else, or from multiple threads)
13:35:02
TeMPOraL
i.e. I'm running trace with :report nil and :print and :print-after set to code logging data
13:36:07
TeMPOraL
now I can't figure out how to get access to the name of the function being currently traced, and after reading the source code, it seems SBCL goes out of its way to ensure I can't access it, including NULLing *current-frame* and rebinding sb-debug:arg in a way that prevents me from accessing the traced function
13:37:06
TeMPOraL
my questions: is there a good reason for preventing one from accessing the traced function like this? should I approach the problem of tracing differently?
14:02:09
pfdietz
fatal: unable to access 'https://git.code.sf.net/p/sbcl/sbcl/': The requested URL returned error: 503
17:57:59
karlosz
stassats: does that gdc transform work for (gcd a (progn (setq a 5) a) when a is 15?
18:25:40
pfdietz
That example works fine. I would expect the random tester to find any bug like that.