Hi, Kevin Ryde <[EMAIL PROTECTED]> writes:
> I know the "values" struct is doing exactly this, but I suspect it's > abusing the vtable system. I suspect that what scm_init_stacks() in > stacks.c is doing is normal (if there's such a thing as "normal"). I'm not sure the indirection in `scm_init_stacks ()' is needed since it uses STACK_LAYOUT for both VTABLE and SCM_STACK_TYPE, and `make-struct' doesn't look at the vtable's vtable anyway (when creating instances of SCM_STACK_TYPE). > Perhaps we have an expert lurking here, but I think make-vtable-vtable > does in fact do what its name suggests: make a vtable for creating > vtables. More generally, a three-level architecture like the one you suggest would look fishy. For instance, GOOPS and other CLOS derivatives have <object> and <class>, representing respectively the "base" and "meta" levels, but they have no need for <class-class>, <class-class-class> or some such. Thanks, Ludovic. _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel
