Dave Benson [EMAIL PROTECTED] writes:
On Fri, Feb 25, 2005 at 12:12:30PM -0500, John Ehresman wrote:
Dave Benson wrote:
a small c program to generate GValue marshallers from the metadata
seems pretty straightforward. such marshallers should probably
be compiled at the same time as the
libffi or something similar a problem ?
I'm not a language binding expert, therefore I just included what is
provided by the .defs plus some obvious additions. Should we make the
introspection api depend on libffi and offer some form of call-by-name
interface + the ability to register type
On Fri, 2005-02-25 at 10:58 +, Gustavo J. A. M. Carneiro wrote:
I'm not saying libffi is bad, if we have computer generated prototype
descriptions. Manually using libffi is more of a problem due to the
human tendency to make mistakes...
Another concern about libffi is portability.
On Fri, 2005-02-18 at 14:42 -0500, Colin Walters wrote:
One thing also that I would also like is a way to sensibly convert a
GError domain/code into a string. For example, mapping
G_FILE_ERROR/G_FILE_ERROR_EXISTS into a DBus error message named
org.gtk.GLib.FileError.Exists that callers can
On Thu, 2005-02-24 at 15:20 -0500, Matthias Clasen wrote:
I have written up a draft spec for the format of the binary metadata
to back up the repository api which I posted earlier. I hope to have
some initial code implementing both of these soon.
guint caller_owns_return_value :
Hi,
Mike Kestner [EMAIL PROTECTED] writes:
One more wrinkle for params...
It would be nice for string params to identify encoding when they are
not in utf8 encoding, such as in the filename case. A case could
probably be made for a GStringDef.
Not sure if this is helpful, but we solved
Trying to attack the introspection problem from the api side.
Here is an initial api proposal for an interface repository.
I imagine this would be implemented on top of metadata blobs
which are mmapped readonly, thus the various *Def objects can
be very lightweight, essentially just a pointer to
