freenode/#clasp - IRC Chatlog
Search
19:31:36
kpoeck
Well according to this, i'd expect (+ most-positive-long-float most-positive-long-float) to cause a trap
19:39:45
Shinmera
Afaiu you need to instruct the CPU's FPU which things should cause exceptions, so some things might also just not be enabled.
19:41:26
kpoeck
Unfortunately my buddy UNDEFINED-FUNCTION (:NAME INLINED-TWO-ARG-/) failed, so I have to recompile all cclasp
19:43:47
kpoeck
and waf now compiles nearly everything from scratch, this build system needs some tender care
20:48:52
kpoeck
(+ most-positive-long-float most-positive-long-float) -> #.ext:double-float-positive-infinity
21:28:19
kpoeck
In line 193 of float-features.lisp, with #-(or abcl ccl clisp cmucl ecl sbcl) don't you need to add clasp?
22:41:58
makomo
now there's a second CLASP: https://www.radioeng.cz/fulltexts/2011/11_04_880_889.pdf :-)
4:07:30
beach
So when there is an error, there is a variable in the stack frame that contains the source information. By using RET in SLIME I can then inspect the source information.
4:17:10
beach
But the source information contains the line and column number of the beginning and the end of the expression being evaluated, and it contains the full text of the code that produced it. So by using the SLIME inspector, I can immediately see what expression is being evaluated.