libera/#clasp - IRC Chatlog
Search
11:05:39
Inline
welp, i'm trying to install the externals-clasp via ros install externals-clasp but it errors out due to it not being able to download stuff from the links in it's script
11:08:45
Inline
a manual download from gos-k s github repo "externals-clasp" and trying to compile it works
11:11:02
Colleen
kpoeck: drmeister said at 2021.10.14 20:44:02: You shouldn't need ffi.h - I'll try and remove it and rebuild everything. I'll also remove all those undef's - I didn't get around to it yet.
11:11:02
Colleen
kpoeck: drmeister said at 2021.10.14 20:54:08: I see what I did - I left some partially tested code I was developing for imgui-clasp that tried to use ffi.h directly. I removed that code and removed the #include "ffi.h" and I'm building now. Question for you though - we test for libffi in ./waf configure - so I thought we needed it elsewhere. Do we need libffi or do we not?
11:17:38
kpoeck
Question: why does core__lisp_implementation_id shortens the id to 8 chars? git rev-parse --short HEAD returns 9 letters
13:07:49
drmeister
::notify kpoeck No reason - I think I just assumed that git would return 8 characters (2^3) - I don't see any reason we can't make it longer. I'll do that.
13:15:48
drmeister
::notify kpoeck Also, it takes the characters from the end of the git rev-parse HEAD result while git rev-parse --short HEAD returns the 9 characters from the left side of the git rev-parse HEAD result. I don't recall why I did that. Do you want the result of git rev-parse --short HEAD to be returned by core__lisp_implementation_id ?
13:57:56
yitzi
I don't think that externals-clasp really works anymore. I was never able to build using roswell also.
14:05:18
drmeister
::notify kpoeck On further investigation I don't know why I took the right 8-most characters from the git rev-parse --short HEAD output for the (core:lisp-implementation-id) I've changed it to 9 characters now. I've also added (core:clasp-git-full-commit) - it returns the full commit hash.
15:07:04
drmeister
The As, As_unsafe and IsA template functions take XXX_sp types as their template arguments.
15:11:48
drmeister
That generates compiler errors all over the place that tell me what the type To_SP::Type() is.
16:18:08
drmeister
Bike: Can you make this work with multiple-value-xxx forms? Here I'm trying to use LOOP and get double-float results out of the LOOP.
16:25:34
drmeister
The question is - how should we write this best and what do we need to support for code that we will find in the wild?
16:29:54
Bike
doing it with multiple-value-bind will take some work. it's sort of a different problem from the floats
16:34:18
Bike
writing it how you did with (multiple-value-bind (...) (... (values ...)) ...) is probably how it ought to be written
16:37:26
Bike
what the compiler needs there is i think two things... one, it should be able to infer types of multiple value call parameters in obvious cases like that
16:38:17
Bike
the former would at least mean you don't need to declare xx etc double-float outside of the loop
16:39:00
Bike
...and, the easier thing to deal with there, is that i haven't done any of these transforms for MAX yet
16:56:37
drmeister
I found the problem with the arithmetic that was causing some normals to be incorrect.
16:57:06
drmeister
The infix:infix macro is good when translating code from a language that uses infix.
17:35:46
Bike
the other easyish thing i can do is change how the contagion transforms work in such a way that the code shouldn't box in the loop even without the "of-type double-float"s, though it would do more type checks