[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: goops C interface
From: |
Eric Moore |
Subject: |
Re: goops C interface |
Date: |
Fri, 27 Oct 2000 12:54:01 -0400 (EDT) |
>>>>> "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)
Re: goops C interface, Mikael Djurfeldt, 2000/10/25
- Re: goops C interface,
Eric Moore <=
- Re: goops C interface, Michael Livshin, 2000/10/27
- Re: goops C interface, Bruce Korb, 2000/10/27
- Re: goops C interface, Carl R. Witty, 2000/10/27
- Re: goops C interface, Dirk Herrmann, 2000/10/27
- Re: goops C interface, Dale P. Smith, 2000/10/27
- Re: goops C interface, Michael Livshin, 2000/10/28