6:04:53beachI'm off to buy food. I'll be back in an hour or so.
7:29:42beachToday I will continue with my code for verifying every object in environment E5.
7:30:18beachBut I keep thinking how close we are to extract at least part of Cleavir to a separate library.
7:31:36beachOnce Clostrum is done, We can extract CST-to-AST, which then includes the AST definitions. To accomplish its task it would then use Eclector, CST, Trucler, Clostrum, and the CST-to-AST code.
7:32:09beachThe only thing that needs to be decided is which part of the existing code counts as generally useful, and which part should be left as client configuration.
7:34:01beachIn that extracted library, we could also supply default versions of some of the macros like DEFUN, DEFMACRO, and the simple ones like WHEN, UNLESS, etc.
9:38:33jackdanielbeach: what should we do with function-unbound? remove it from the specification or leave it be?
9:39:05beachI say leave it in. I suspect I had good reasons to include it.
9:40:09jackdanielOK, I think that its description should be clarified in that case, because based on the rest of the specification it is not clear, how the "client code can use the return value of this function to determine whether function-name is unbound"