Bug 124406 – [GTK] Mark all deprecated symbols in GObject DOM bindings

• Status: RESOLVED
• Resolution: FIXED
• Component: Bindings

[Carlos Garcia Campos]

We have custom (as not autogenerated) and deprecated symbols all in WebKitDOMCustom. The deprecated methods in WebKitDOMCustom are not marked as deprecated and they don't appear in the right documentation section, but all of them are mixed in WebKitDOMCustom, see:

http://webkitgtk.org/reference/webkitdomgtk/2.3.1/webkitdomgtk-WebKitDOMCustom.html

The deleted objects (also deprecated) are not included in the documentation either.

[Carlos Garcia Campos]

Created attachment 217041 [details]
Patch

[Carlos Garcia Campos]

Created attachment 217391 [details]
Updated patch

Just rebased.

[Gustavo Noronha (kov)]

Comment on attachment 217391 [details]
Updated patch

View in context: https://bugs.webkit.org/attachment.cgi?id=217391&action=review

LGTM with one minor nit:

> Source/WebCore/bindings/gobject/WebKitDOMDeprecated.cpp:22
> +#if !defined(WEBKIT_DISABLE_DEPRECATED)

I don't think we want this in the implementation file, just on the header, since it's something that should be used only by stuff that use WebKit at build time only.

[Carlos Garcia Campos]

(In reply to comment #3)
> (From update of attachment 217391 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=217391&action=review
> 
> LGTM with one minor nit:

Thanks for the review.

> > Source/WebCore/bindings/gobject/WebKitDOMDeprecated.cpp:22
> > +#if !defined(WEBKIT_DISABLE_DEPRECATED)
> 
> I don't think we want this in the implementation file, just on the header, since it's something that should be used only by stuff that use WebKit at build time only.

I'm not sure I get it. This is not used internally, when WebKit is built without deprecated symbols we don't want the implementations either, otherwise we will have a bunch of non static methods without a prototype.

[Gustavo Noronha (kov)]

What I mean is defining WEBKIT_DISABLE_DEPRECATED is not something we would do while building WebKit itself, it's something that people who depend on/link with WebKit will use, only. We want the symbols to always be in the library, the define exists only to make the prototypes disappear for API users at their build time, not WebKit's. Makes more sense put this way?

[Carlos Garcia Campos]

(In reply to comment #5)
> What I mean is defining WEBKIT_DISABLE_DEPRECATED is not something we would do while building WebKit itself, it's something that people who depend on/link with WebKit will use, only. We want the symbols to always be in the library, the define exists only to make the prototypes disappear for API users at their build time, not WebKit's. Makes more sense put this way?

Of course you are right, this is not an option to build webkit itself, thanks for the explanation. I'll remove it also from the generated code before landing.

[Carlos Garcia Campos]

Committed r159614: <http://trac.webkit.org/changeset/159614>