Marcus Crestani wrote:
KKCC traverses every Lisp object only once: When KKCC encounters a
vector for the first time, it follows its outgoing pointers to other
Lisp objects and sets the vector's mark bit. When the traversal hits
the same vector again, it is not processed again, since the mark bit
Does this help?
Yeah. I was just trying to figure out a way to avoid the 1012 bytes per
page of wasted space but i guess it isn't too important. i've already
created a separate `char-subtable' type for the subtables that has
nothing but an array of 256 lisp objects.