[Webkit-unassigned] [Bug 133726] [GTK] Limit the amount of API exposed to GObject DOM bindings API

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 11 03:00:47 PDT 2014


--- Comment #1 from Carlos Garcia Campos <cgarcia at igalia.com>  2014-06-11 03:01:11 PST ---
An alternative would be to split our current API in stable/unstable, which I think it's similar to what apple does (they call it public/private, though). We have a very limited API declared stable and included by the main header webkitdom.h. This would be API/ABI stable . The rest of the API is considered unstable, and it can change. We only need to care about the ABI in this case I guess, since it's the same library in the end. The unstable API wouldn't be included by the main header, so that people have to explicitly include every header to use it. We could also force people to define a typical macro THIS_IS_UNSTABLE_AND_I_KNOW_WHAT_I_AM_DOING.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list