freenode/#clasp - IRC Chatlog
Search
22:15:50
attila_lendvai
can you think of a definition that has a relatively unique name that I could grep for to see how its C++ implementation is replaced by a lisp reimplementation?
22:17:12
attila_lendvai
Bike: a short bird's eye view would definitely help me here, but detailed docs cost programmer time that can be put to rather bringing the codebase closer to a readable documentation
22:19:27
karlosz
a lot of useless computation coud be saved while compiling by doing some math to figure out how to keep accessory information correct and not just recomputing it every time in a loop
22:23:15
karlosz
maybe a declarative macro interface declaring what information gets changed/needs to be recomputed for each individual pass and some manager that can figure out how to recompute things from that info
22:25:22
attila_lendvai
looks like I'll have to take a deep breath and look at the code itself... I'm not overly excited about the details of ld and C++ internals, but I learned programming in m68k asm, so I should have the means if I can muster the motivation...
22:26:24
attila_lendvai
but the clasp codebase could be improved plenty to be more welcoming to newcomers
22:30:41
Bike
attila_lendvai: i mean, it's pretty much that there's an iclasp executable, and when you run cclasp you have it load a bunch of fasls that do redefinitions
22:38:04
attila_lendvai
this is what I'm aiming to address with a more structured bootstrap: clasp-builder.lisp is full of weird tagbody-go code because iclasp is very limited, but it's the same code that is run to build cclasp, i.e. when full CL is available. this is an unnecessary waste of programmer brain cycles.
22:55:46
attila_lendvai
the wscript gives a list of files to compile/load-a/b/cclasp, that then arbitrarily filter out ranges of that list using the filenames at the expected start/end indexes. and I wonder why I don't understand what's going on...