freenode/#clasp - IRC Chatlog
Search
3:20:39
karlosz
on another note, drmeister: the arch thing people were running into with the boost symbol disaappeared when i reverted to a May 20th version of clasp
3:22:14
karlosz
i started the build a few hours ago on my laptop and it still hasnt finished though so i dont think its possible for me to bisect this issue
3:31:11
karlosz
and clasp bundles waf right? so is there an easy way to use the systems or wait for clasp to update it?
4:08:28
drmeister
The usual strategy for this kind of implementation is to write it all in C++. The latency requirements are too strict to do otherwise. Once you start down this road, you never stop: your life as an implementor is that of a powerful, bitter C++ wizard.
4:08:45
drmeister
https://wingolog.org/archives/2015/11/03/two-paths-one-peak-a-view-from-below-on-high-performance-language-implementations
4:27:14
karlosz
is there an incanctation for only rebuilding the ceavir part of clasp? i am used to making a small change or print statements in cleavir and starting a quick self compile to check my work
4:45:31
scymtym
beach: i'm getting close to pushing the parse result protocol to the eclector master branch. if you have time, could you have a brief look at the documentation and tell me whether it makes sense to you? the current version is https://techfak.de/~jmoringe/eclector.pdf , section 2.4 is about the new package and protocol
13:44:52
beach
Sure. I am convinced that I can use it in Second Climacs from that documentation. Right now I am working more on SICL, though.
13:45:23
drmeister
I need to push out some changes and git doesn't work through the terminal for some bizarre reason