0:10:34an_origamian*All* C++ code that wants to interact with clasp must use waf? (as described here: https://clasp-developers.github.io/clbind-doc.html)
0:10:42an_origamianIf that is the case, is that code required to be licensed under LGPL like clasp is?
0:22:13an_origamianI am also unsure where that directory structure at the top of the page comes from since I don't see that in the repo or in my filesystem (I installed from AUR).
0:23:45yitziTo use clbind you need clone from github and follow the instructions in the wiki to build. We no longer use waf, so the clbind documentation needs to be updated.
0:27:41an_origamianDoes that mean I can't use C++ with AUR version?
0:32:29yitziI don't believe so. Pretty sure we don't currently have the ability to dynamically add extensions, therefore they are linked directly with the clasp binary.
0:33:30yitziYou are already using the AUR version which is building from scratch. Building on AUR is easy. That is my base OS and I wrote the AUR and new build system.
1:17:32Bikeon further reflection i think to avoid the unwind protect we may need to set the stack pointer in the unwinder itself
1:17:44Bikewhich... shouldn't be too expensive or anything, but it's a little weird
1:46:09Bikethat's more closely analogous to the native unwinder... but also there's no real way to inform it... bleh
1:47:09Bikei guess i could define a new dynenv class specifically for vm frames, that just records the frame pointer to unwind to
1:47:41Bikethen the unwinder can do that without going through longjmp. so we'd still be stack consing dynenvs and all, but it would at least be somewhat cheaper than an unwind protect dynenv
1:57:20Bikeand we wouldnj't be setjmping for every call, so that's nice.