Re: goops C interface

[Eric Moore]

>>>>> "Mikael" == Mikael Djurfeldt <address@hidden> writes:

Mikael> guile-snarf.h and fdi.c example is just experimental code to
Mikael> see if that style of usage is a good thing.

Mikael> I actually dislike adding the slots incrementally.  Since
Mikael> there is no "finalize" construct, this puts bad constraints
Mikael> onto the implementation.

That opens 2 questions I'll put up for comment :)

1) do people prefer some kind of giant varargs style function that
   defines a class, or one that takes a struct that defines it?
2) should the API deal in SCM values (since a goops object can by
   default hold any value) or C values (like the fdi.c and snarfing
   system does)