Search
Thursday, 24th of November 2022, 2:43:37 UTC
5:13:16
nij-
I've just watched this nice talk again https://www.youtube.com/watch?v=8X69_42Mj-g Got a bit confused.. seems that the goal is to use C++ libs easily in CL. But why go all over the ways? Can't we just use CFFI to glue CL and C++ with C?
5:30:33
drmeister
whereiseveryone: yes - we just added the feature to start/run/shutdown clasp as a library
5:35:48
drmeister
We haven’t set up clasp to build as a library yet. That would require a bit of work with the build system.
12:37:09
consolers
does the released clasp 2.0 have a chance of building with llvm 13 at all?
12:38:17
consolers
I've gotten as far as getting koga to dump a build script without sbcl/asdf
13:01:08
consolers
but i cant spot how or where generated/cclasp-translations.lisp is generated
13:16:46
yitzi
consolers: We require llvm14
13:18:18
yitzi
If have to build with llvm13, there is a "llvm13" branch which is old.
13:18:40
consolers
i'm just loath to upgrade it on gentoo
13:18:46
yitzi
No promises regarding its usefulness
13:19:50
consolers
by default gentoo would upgrade upto llvm15
13:20:44
consolers
i'll check again later. later
13:21:04
yitzi
nij-: CFFI doesn't really interface with C++. It relies on extern "C" basically.
14:14:00
nij-
Yes, but we can let CL and C++ talk to each other via C.
14:14:27
nij-
I wonder what's the advantage of clasp approach over my naive approach.
14:16:30
yitzi
With Clasp you can write C++ classes that show up as Lisp classes.
14:17:32
yitzi
And using C as a bridge to C++ is a PITA.
14:18:02
jackdaniel
doesn't clasp also make the other way possible?
14:18:27
jackdaniel
i.e cl class as c++ class
14:19:58
nij-
yitzi is it more a PITA than implementing the whole CL?
14:20:06
nij-
(gotta leave for a while.. brb)
14:20:20
nij-
I mean, in theory, CFFI is "enough", right?
14:20:41
nij-
There must be some other optimization issue for the author of clasp to implement it.
Thursday, 24th of November 2022, 14:43:37 UTC