libera/#clasp - IRC Chatlog
Search
14:24:12
yitzi
There is still differences between the scraper output of ccl and sbcl, but it builds.
14:25:06
yitzi
I am trying to make the output identical from each lisp, including the whitespace in C wrapper functions.
14:26:52
Bike
usually 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:28:22
yitzi
Just seems like a bit of uneeded complexity. Using print-logical-block would maybe be better?
14:29:43
yitzi
I'm just talking about line wrapping, etc. ... if that wasn't clear. You are correct, that the order has to be fixed in the scraper.
15:18:58
drmeister
Can't we boot with Clasp now? We have a full Common Lisp in the bytecode compiler.
15:19:43
Bike
i think we're already set up to use clasp to build itself? i think yitzi mentioned that
15:20:57
drmeister
We could use autotools/configure to build clasp and then use clasp to run koga to build the rest of it.
15:22:39
Bike
it 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:48
Bike
one 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:11
Bike
but 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
22:47:03
Bike
among the possibly literal thousands of warnings on cando, there are a couple important ones like infinite recursion and use of uninitialized variables
22:47:23
Bike
but mostly it's a ton of unused variables, and that's not even including all the places where that warning is specially disabled