Hi, Josselin Mouette wrote:
No, what can be done is to fix upstream's broken declaration that 'you can assume glib functions are available when doing "#include <gtk/gtk.h>"'. It doesn't follow that just because this works in practice, it should be a supported usage.
When many of the types used by GTK+ are those provided by GLib, it sounds wrong to ask developers to include the GLib headers to have these types available.
If it is really expected that type declarations are to be shared between a program and a library, then the program becomes dependent on the library's ABI without this dependency being formally expressed in any usable form, which is broken in and by itself.
GTK needs to provide its own definitions of types and not expose interfaces it does not control.
Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
