14:38:40drmeisterI pushed the changes to 'dev' - it should build on linux and OS X
14:47:39drmeisterI had to do some commenting out in clasp_gc.cc. The static analyzer crawls into all C++ classes and exposes offsets of fields. The mutexes that we added have fields on Linux that are not present in OS X.
14:47:53drmeisterI'll have to tell the static analyzer to ignore them.
15:20:24drmeisterBike: So you want translators that convert claspCharacter (32bit 'int' character) to and from T*
15:22:48BikeclaspChar (or whatever the base-char one is) as well
20:40:31Serenitty[m]And I didn't have to change a single thing in the code from the dev branch.
20:42:18Serenitty[m]My only complaint at this point is that I get those linking warnings at runtime whenever I compile any code. Is there a way to supress these?
20:49:04Serenitty[m]Oh, I know you're working on fixing the warnings. My question is just if in the meantime, there's a way to configure LLVM not to give them.
20:58:12drmeisterTrying the acid test now of turning on fastgf in bclasp to build cclasp
20:59:43drmeisterSerenitty[m]: The cclasp compiler is slow - it uses generic functions a LOT and generic functions weren't very fast in cclasp - that will hopefully change now that fastgf is (hopefully) coming online.
21:00:12drmeisterSo slime takes about 10 min to compile.
21:05:15Serenitty[m]So, now I'm curious, how do I write C++ code that interfaces with Lisp code? Is there a library that I need to link it with? I couldn't find any documentation about that.
21:24:07drmeisterThere are two example repositories - hang on.