Re: DEFSTRUCT and reclaimable storage

[Alan Bawden <ALAN at MIT-MC>]

Well, I'm not actually sure that this is really something that belongs
in defstruct.  Defstruct already has an amazing amount of hair in it.
(The code you were looking at is about to be replaced by a newer
version with even more features.)

Is there some reason that what you want has to be made part of
defstruct itself?  Is there some reason I can't see that prevents you
 from simply writing the alocator you describe?