libera/#clasp - IRC Chatlog
Search
13:31:23
kpoeck
::notify drmeister: In 9b456cc6f380ca5cefcc873c8fd2cb677470e5a4 you fixed something I fixed some commits earlier. The #undef .. don't seem to necessary since I dropped the #include that caused the symbols to be defined twice
14:47:09
drmeister
We check if libffi is available but we don't use it in clasp code. Do you have any thoughts on that?
16:28:23
drmeister
frgo: I'm using clbind for binding to imgui. clbind doesn't handle variadic functions - so I'm figuring out that.
16:34:18
drmeister
In the most general case it's clunky because I have to manage memory for all of the arguments of different types.
17:52:07
frgo
drmeister: What do you struggle with exactly? I have never had the need to go for low level libffi fiddling. I just used CFFI with libffi just being used behind the scenes.
18:06:00
frgo
drmeister: And you are aware of https://common-lisp.net/project/cffi/manual/html_node/foreign_002dfuncall_002dvarargs.html ?
18:07:09
frgo
Ah - yes. C++, well. Make a wrapper function in C for that C++ function and that's it. It's tedious, yes, but...
18:50:18
drmeister
Am I thinking about this wrong? It looks like a tremendous amount of work to wrap something like printf.
18:50:52
drmeister
I have to convert every Common Lisp value into a C Plain Old Data type and manage memory for it and then clean up after the call.
19:00:22
frgo
For this reason CFFI provides said macro ... I can't say what it takes for clbind to support varargs C++ function/method calls..
19:02:07
frgo
I've always done that as much as possible in Lisp land and only very rarely done that in C land.