3 Commits

Author	SHA1	Message	Date
Ryan Lortie	bceaf3a719	glib-private: #include <glib.h> ... This is really our only choice if we don't want to annoy the single-include checking when we use this from inside of gio.	2011-09-09 16:05:55 -04:00
Ryan Lortie	d86386159d	glib worker: move to glib-private framework ... Remove the private glib_get_worker_context() symbol and move it over to using the glib-private stuff like GWakeup is doing. https://bugzilla.gnome.org/show_bug.cgi?id=657992	2011-09-09 14:32:00 -04:00
Colin Walters	9bf59d4a14	Add glib__private__() API to share between glib,gio; port GWakeup to it ... Historically we've added random symbols to the public API with warnings that they're private; examples are: glib_gettext(), glib_pgettext() g_thread_functions_for_glib_use, g_thread_use_default_impl, etc. And we almost added "GWakeup" to public API just to share between glib and gio. This new glib__private__() API exports a hidden vtable, and adds a macro GLIB_PRIVATE_CALL() that makes it generally convenient to use. This adds an extremely tiny cost for the double indirection; but it has the benefit that we don't need to either: 1) compile the code into both glib and gio (like GWakeup), with the inefficiency that implies. 2) Export a "do not use this" symbol; the serious problem with this is that someone CAN use it pretty easily. Particularly if we document it. It's far, far harder to peek into a structure without a public header file. https://bugzilla.gnome.org/show_bug.cgi?id=657992	2011-09-09 14:17:08 -04:00