It's yet another type next to objects/interfaces and `GVariant` that has
floating references.

The result of commit 9c674ad3, but until
we have an installed copy of GLib >= 2.79, the warning tests are
disabled.

A few applications such as gnome-music load the GIRepository typelib
and use it to adjust their search paths.

GLib 2.79.x now provides libgirepository-2.0.so.0 (GIRepository-3.0),
but each OS distribution is likely to have a transitional period during
which GLib's libgirepository-2.0.so.0 has become available, but bindings
like PyGI and gjs are still linked to gobject-introspection's
libgirepository-1.0.so.1 (GIRepository-2.0).

During this transitional period, interpreted languages that load the
GIRepository namespace could get the "wrong" version, which will result
in adjusting a search path that will not actually affect the language
binding's typelib lookup, and could also lead to symbol and type-system
conflicts.

We can avoid this collision by making GLib's GIRepository library refuse
to load versions of the GIRepository typelib that are not 3.0, and
similarly making gobject-introspection's GIRepository library refuse to
load typelib versions that are not 2.0. A relatively neat way to achieve
that is to make each version behave as if the other one doesn't exist.

Signed-off-by: Simon McVittie <smcv@debian.org>

We already had one of these tests for strings. Add them comprehensively
for other types as well, to cover the case where a C function doesn't fill
in an out parameter; for example, in an early return.

See gjs#591.

Language bindings may need to canonicalize these NaNs if the language has
only one permissible bit representation of NaN. (JavaScript has only one
NaN, and runtimes store other information in the bit-space occupied by
noncanonical NaNs.)

See: gjs#591

Philip Withnall authored Nov 07, 2023 and Philip Chimento committed Jan 03, 2024

Signed-off-by: Philip Withnall <pwithnall@gnome.org>

Resolves: https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/488


Signed-off-by: Simon McVittie <smcv@debian.org>

Many virtual functions definitions are still documented using the
gtk-doc struct field style, as opposed to a full docblock near the
function pointer.

We should still favour the full docblock, as it can contain an
appropriate description and annotations for arguments and return values;
but if there is no block we can at least try to see if there's a field
description to fall back to, to avoid fully undocumented symbols.

Fixes: #478

We currently are not including the description for function pointer
fields inside classes. This means older gtk-doc descriptions are
completely ignored.

While we want the gir to expose those functions, eg for
documentation purposes, bindings will usually not be able to
introspect them, and should be aware of the inline specifier.

Adding a new attribute would make a bunch of symbols that cannot be
called by language bindings suddenly appear in the GIR data, which would
not be great for backward compatibility.

They don't exist in the shared library, so they should always be marked
as not introspectable; this means inline symbols are not available to
language bindings that use FFI to call into C.

A variant of `method` for inline functions.

A variant of the `function` element for inline functions.

Co-authored-by: Evan Welsh <contact@evanwelsh.com>

We don't want to add the giscanner/ subdirectory of the source or build
root to the sys.path or PYTHONPATH, because that would cause our ast.py
to shadow the Python standard library's ast module.

Instead, add the source and build roots (only) to the search path, and
always import the extension module as part of the giscanner namespace.

Resolves: https://gitlab.gnome.org/GNOME/gobject-introspection/-/issues/429


Signed-off-by: Simon McVittie <smcv@debian.org>

Meson copies Python source into the build directory, so that we can
rely on being able to import compiled C extensions and Python code
from the same place.

Signed-off-by: Simon McVittie <smcv@debian.org>

This is used by Meson's generate_gir call.

See: https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3892

Simon McVittie (Collabora) authored Feb 09, 2024 and Philip Chimento committed Feb 29, 2024

In the project from which this copy of cmph was forked, this was fixed
in version 2.0.2 by commit
https://sourceforge.net/p/cmph/git/ci/bbf77c63c9e87b0675209fadf53a36528e38bb03/



Signed-off-by: Simon McVittie <smcv@collabora.com>

Otherwise we'll have to escape the regexp.