delta/glib.git/gobject/gparam.c, branch require-python34

gobject: Fix typo in documentation for g_param_spec_get_default_value()

2017-11-01T11:13:27+00:00

Signed-off-by: Philip Withnall

Use hash tables as sets in various places

2017-10-26T11:27:17+00:00

Where we were already treating GHashTables as sets, modify them to use
the set-specific APIs g_hash_table_add() and g_hash_table_contains(), to
make that usage more obvious and less prone to being broken.

Heavily based on patches by Garrett Regier .

Signed-off-by: Philip Withnall 

https://bugzilla.gnome.org/show_bug.cgi?id=749371

gobject/: LGPLv2+ -> LGPLv2.1+

2017-05-24T09:58:19+00:00

All gobject/*.{c,h} files have been processed.

gmarshal.c and gmarshal.h don't have a license header.

https://bugzilla.gnome.org/show_bug.cgi?id=776504

GParam: make G_PARAM_USER_MASK unsigned

2016-12-02T19:10:26+00:00

UBSan considers left-shifting a negative number to be undefined
behaviour (per
 it is
implementation-defined in C89, but according to
 it is undefined in C99).

Signed-off-by: Simon McVittie 
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=775510
Reviewed-by: Colin Walters

introspection: use (nullable) or (optional) instead of (allow-none)

2016-11-22T22:14:37+00:00

If we have an input parameter (or return value) we need to use (nullable).
However, if it is an (inout) or (out) parameter, (optional) is sufficient.

It looks like (nullable) could be used for everything according to the
Annotation documentation, but (optional) is more specific.

glib: Add missing (nullable) and (optional) annotations

2015-11-07T09:48:32+00:00

Add various (nullable) and (optional) annotations which were missing
from a variety of functions. Also port a couple of existing (allow-none)
annotations in the same files to use (nullable) and (optional) as
appropriate instead.

Secondly, add various (not nullable) annotations as needed by the new
default in gobject-introspection of marking gpointers as (nullable). See
https://bugzilla.gnome.org/show_bug.cgi?id=729660.

This includes adding some stub documentation comments for the
assertion macro error functions, which weren’t previously documented.
The new comments are purely to allow for annotations, and hence are
marked as (skip) to prevent the symbols appearing in the GIR file.

https://bugzilla.gnome.org/show_bug.cgi?id=719966

Doc: fix some gtk-doc warnings

2015-10-30T14:30:55+00:00

https://bugzilla.gnome.org/show_bug.cgi?id=755364

gparam: Fix Since tag of g_param_spec_get_name_quark

2015-09-08T12:15:44+00:00

Add a method to get the pspec name quark

2015-09-08T00:54:01+00:00

This lets us avoid the quark lookup in the hot
property change notification path.

Simplify g_param_spec_get_redirect_target a bit more

2015-09-07T07:02:11+00:00

It is enough to look for exact matches here, so no need to
dive into g_type_instance_is_a and take locks, etc.