[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 07:08:27 PDT 2014


--- Comment #4 from Carlos Garcia Campos <cgarcia at igalia.com>  2014-06-11 07:08:49 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> > hmm, we would still need a way to split new unstable api added to stable classes. I guess the code generator could use the symbols file to know which symbols are stable. We don't have signals and for properties we always generate at least a getter, so it will be a new symbols in the symbols file. New symbols that are not in the stable symbol list would be added to a FooUnstable.h header, for example. The problem is that the property would be added to the class in any case, although changing a property doesn't actually break the API/ABI (you will get a runtime warning)
> We could, although it would be super ugly, call those properties something like whatever-unstable.

But when we make those stable, the name will change so and people will have runtime warnings in any case.

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