11:19:48scymtymdrmeister: you mean s-expression support for the leap parser? i didn't update that. i made the feature branches a year ago and did touch the repository since then
19:23:23Bikesomething funny's happening with shared-initialize and satiation. there's a first dispatch miss i don't mind, and the log has the whole call history there. but the next dispatch miss the call history is empty
20:45:34shihodrmeister: I got the error use of overloaded operator '=' is ambiguous (with operand types 'gc::Nilable<AtomOrBondMatchNode_sp>' (aka 'Nilable<smart_ptr<chem::AtomOrBondMatchNode_O> >') and 'chem::BondMatchNode_sp' (aka 'smart_ptr<chem::BondMatchNode_O>')) obj->_FirstTest = chain->chain_get_head();
20:57:03Bikedoesn't look like it needs to be exposed.
20:57:39Bike1+ and 1- are defined in foundation.lsp in the obvious way.
20:58:06kpoeckOK, than I make a pr not exposing them (and I fix the edge cases)
20:59:32kpoeckstassats: thanks for pointing to one-plus, didnt see that
21:12:38drmeisterI'm going to start saving all symbol tables for all loaded fasls in memory.
21:13:39drmeisterIn the last week I wrote code to walk all fasls in memory and load their counterparts from disk to search their symbol tables every time a backtrace is generated.
21:14:07drmeisterBut there are problems with this. fasls disappear - in particular slime C-c C-c generated fasls disappear.
21:17:25drmeisterI'm setting up code that will build a compact symbol table each time a fasl is loaded and I'll search that when we generate backtraces.
21:17:36drmeisterI can also use the symbol tables for DISASSEMBLE