Re: scheme_make_class_assembly

[Matthew Flatt <mflatt@cs.utah.edu>]

Quoting Greg Pettyjohn:
> I'm trying to make a class using scheme_make_class_assembly.

This may not be a good idea in the long run. The function is a
candidate to disappear in the next release, as the whole class system
is removed from the core interpreter and replaced with a set of macros.

scheme_make_class() will be re-implemented in a utility library, and
maybe scheme_make_class_assembly(), too. But it would be better to
avoid it.

Are you doing something that couldn't be done just as well in Scheme
code? (Depending on what you're doing, I imagine that may require
exporting some C-based functions for the Scheme code to use as
methods.)

> The only thing that comes to mind, is that I should provide at least one for
> the number of interfaces
> (2nd param)
> to scheme_make_class_assembly
> 
> Is this correct?

No, I don't think that's it.

What kind of superclass are you using with scheme_create_class()? More
specifically, is it object%, a Scheme-implemented class, or a
scheme_make_class()-implemented class?

Matthew