GNOME Bugzilla – Bug 726037
Add G_PARAM_READWRITE value to the GParamFlags enumeration
Last modified: 2014-11-10 22:27:14 UTC
The introspection scanner cannot resolve the G_PARAM_READWRITE #define, so we need to help it out ourselves.
Created attachment 271435 [details] [review] gparam: Annotate G_PARAM_READWRITE This avoids having to re-define it inside language bindings.
this is less useful than I hoped, since it generates a GObject.PARAM_READWRITE symbol outside of the GObject.ParamFlags type. it would be better to just get rid of the #define and add G_PARAM_READWRITE to the GParamFlags enumeration.
Created attachment 271437 [details] [review] gparam: Add G_PARAM_READWRITE to GParamFlags Using a #define for an enumeration value buys us nothing, and it's mostly historical baggage that makes binding GObject needlessly complicated.
Review of attachment 271437 [details] [review]: Looks fine, but can it wait? We've been bitten before by bizarre unintended effects caused by moving things between enums and defines, and we are past API freeze at this point...
to be fair, I don't see any reason why this would break anything, but if you feel more comfortable with punting it for 2.42 that sounds fine by me.
freeze past, master has been branched. Attachment 271437 [details] pushed as 6c39524 - gparam: Add G_PARAM_READWRITE to GParamFlags
Created attachment 277085 [details] [review] docs: Update GParamFlags docs. Remove reference to G_PARAM_READWRITE from GParamFlags' description, since commit 6c395244a5db added G_PARAM_READWRITE to GParamFlags.
Found this little remainder ^.
Review of attachment 277085 [details] [review]: looks good.
Attachment 277085 [details] pushed as 1edd463 - docs: Update GParamFlags docs.