GNOME Bugzilla – Bug 730658
Deprecation warning for non-deprecated type GParamFlags
Last modified: 2014-07-09 13:42:20 UTC
Currently the generated docs for gobject show a deprecation warning for GParamFlags, even though they are not deprecated (also for /unstable/): https://developer.gnome.org/gobject/stable/gobject-GParamSpec.html#GParamFlags
mclasen just figured out more: <mclasen> it indeed gets confused by G_PARAM_DEPRECATED <mclasen> take that out and it doesn't think it is deprecated anymore
After greping a bit, I suspect (didn't test) this part of gtkdoc-scan catches G_PARAM_DEPRECATED and misinterprets it: # If we find a line containing _DEPRECATED, we hope that this is # attribute based deprecation and also treat this as a deprecation # guard. if ($deprecated_conditional_nest == 0 and m/_DEPRECATED/) { $deprecated_conditional_nest += 0.1; }
see also: https://bugzilla.gnome.org/show_bug.cgi?id=731417
Created attachment 279389 [details] [review] tests: Add an enumeration value with DEPRECATED in its name This should not mean that the enumeration is deprecated.
Created attachment 279390 [details] [review] scan: Ignore enumeration fields with DEPRECATED in their name GParamFlags should not be declared deprecated just because it has a value called G_PARAM_DEPRECATED.
the two patches above rely on the two patches for bug 731417, which solve a similar problem for macros.
The following fixes have been pushed: 776edf4 scan: Ignore enumeration fields with DEPRECATED in their name f5daece tests: Add an enumeration value with DEPRECATED in its name
Created attachment 280270 [details] [review] scan: Ignore enumeration fields with DEPRECATED in their name GParamFlags should not be declared deprecated just because it has a value called G_PARAM_DEPRECATED.
Created attachment 280271 [details] [review] tests: Add an enumeration value with DEPRECATED in its name This should not mean that the enumeration is deprecated.