13:05:33yitzi::notify consolers I am pretty sure the reason for the differences in the output of the scraper is due errant whitespace in the C function signature parsers.
13:05:34Colleenyitzi: Got it. I'll let consolers know as soon as possible.
14:19:20yitziLooks like I've "booted" clasp with ccl.
14:22:25Bikeusing it for the scraper you mean? nice
14:23:39yitziCorrect. And to run koga. And whatever other lisp usage was in build.ninja
14:24:12yitziThere is still differences between the scraper output of ccl and sbcl, but it builds.
14:25:06yitziI am trying to make the output identical from each lisp, including the whitespace in C wrapper functions.
14:26:09yitziOne idea would be to use clang-format on the generated headers. Is that crazy?
14:26:52Bikeusually i think it's better to fix such things at the source - so probably like using vectors or something instead of hash tables to get the order consistent
14:27:34yitziclang-format won't change the order. Just newlines, etc.
15:20:07drmeisterThen we don't have a Common Lisp dependency.
15:20:57drmeisterWe could use autotools/configure to build clasp and then use clasp to run koga to build the rest of it.
15:21:04drmeisterACTION is kidding about autotools.
15:22:39Bikeit would be good to make things portable if we can - as soon as we depend on only booting on clasp it's likely we'll become dependent on that, and then we won't be able to build clasp without having a clasp binary
18:39:48Bikeone of the many clang warnings complains when something is declared as a struct and a class in different places, which is actually totally fine in C++, but for some ridiculous reason microsoft mangles names differently if they're structs
18:40:11Bikebut i don't think i can fix that without fixing the scraper/analyzer? code generator to keep track of classes versus structs, and that would just be a lot of work probably