Re: gvector question

> If this comes up in the ANSI tests, do you remember
> which test(s) provoked it ?

it didn't.  i needed to use it to test if a structure had
slots before performing *print-level* truncation.

first of all, i was misusing sd-slots.  i was passing it
a structure instance instead of the result of struct-def.

the cdr of sd-slots is where the slots actually begin.
the *print-length* logic in write-a-structure was broken
because it thought that the car of sd-slots was a slot
(or at least it was counting it as a slot when figuring
out how much to print).  did that change at some point in
the past?  changing the sd-* functions to use svref has
the side-effect of throwing a type-error if one tries to
pass it a structure.

there may be some more low-hanging fruit in the remainder
of failures.. i'm just not sure which ones yet.  there are
a bunch of pathname and subtypep tests that probably are
more than a simple fix.  i was going to start looking at
the compile-file errors.