summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Test enum members starting with a numberebassi/issue-418Emmanuele Bassi2022-02-177-19/+142
| | | | | Add a test to the Regress test suite, with an enumeration type that contains members that would start with a numeric value once tokenized.
* scanner: Validate members of enumeration typesEmmanuele Bassi2022-02-171-0/+12
| | | | | | | | | | | | | | | | Members of enumeration types should not have a name that starts with a number, as that will inevitable break languages that do not allow identifiers to start with a numerical value. To avoid any grief, we change the name to begin with an underscore: GDK_2BUTTON_PRESS -> Gdk.EventType._2BUTTON_PRESS QMI_NAS_RADIO_INTERFACE_5GNR -> Qmi.NasRadioInterface._5GNR We also emit a warning when using strict validation mode, so we give a chance to projects to bail out before committing to a bad API. Fixes: #418
* scanner: Enable warnings in strict modeEmmanuele Bassi2022-02-171-0/+1
| | | | Passing `--strict` implies `--warn-all`.
* Clean up the Git ignore fileEmmanuele Bassi2022-02-171-151/+4
| | | | | We don't use Autotools, and we don't generate files inside the source directory any more.
* Rename the main development branchEmmanuele Bassi2022-02-174-13/+28
| | | | | The main development branch of GObject Introspection is now called "main", following the change in GLib and GTK.
* gitypeinfo: Add pointer-stuffing functions for GITypeTag storage typePhilip Chimento2022-02-162-20/+84
| | | | | | | | | | | | | | | | | | | | | This adds gi_type_tag_argument_from_hash_pointer() and gi_type_tag_hash_pointer_from_argument(). They do the same thing as the corresponding g_type_info_... functions, which are used to pack and unpack the correct field of a GIArgument into/from a data pointer in GHashTable or GList, regardless of machine architecture or endianness. These functions take a GITypeTag obtained from g_type_info_get_storage_type(), instead of a GITypeInfo pointer. (The storage type is the only piece of data that is actually used from the GITypeInfo structure.) It's intended for bindings using an argument cache, such as GJS and PyGObject, so that they don't have to store a whole 64-bit GITypeInfo pointer in their cache in many common cases, and can just store the 5-bit type tag instead. The original g_type_info_... functions are reimplemented in terms of the new g_type_tag... functions.
* Post-release version bump to 1.71.1Emmanuele Bassi2022-02-141-1/+1
|
* Release gobject-introspection 1.71.01.71.0Emmanuele Bassi2022-02-141-0/+19
|
* scannerparser.y: Include io.h on WindowsChun-wei Fan2022-02-131-0/+4
| | | | | We need it for close(), especially when unistd.h is not available, such as in the case of Visual Studio-style builds.
* bdz.c: Some cleanupsChun-wei Fan2022-02-131-9/+1
| | | | | | | | We can just update the for loop condition to be >0 for all builds, which is actually equivilant to >=1 as we are essentially comparing an unsigned 32-bit int, so that we don't need to worry about fixing the VS2012 bug invasively, as Visual Studio 2012 x64 is more sensitive about sizes of variables (e.g. pointer sizes in this case)
* brz.c: Consider _WIN64 for 64-bit pointers tooChun-wei Fan2022-02-131-8/+12
| | | | | | | | | | | The __ia64 and __x86_64__ macros are defined for GCC but not Visual Studio, but actually this code path should also be taken for Visual Studio when doing a 64-bit build (x86_64/x64 and aarch64/arm64, _WIN64 will be defined for these cases), since Windows is an LLP64 platform. This will avoid C4311/C4312 warnings on Visual Studio builds, which are often warnings of concern as we are dealing with pointers with differing sizes on 32-bit and 64-bit Windows builds.
* brz.c: Avoid C4715 warningsChun-wei Fan2022-02-131-1/+3
| | | | | | | | | Later GLib versions assume that warning C4715 is an error as we want ot be sure that functions that return a value do indeed return one by all means. Avoid this warning by adding a 'return 0' in brz_search_packed(), it might be pointless but does indeed avoid the warning.
* docs: Add missing versioned indicesEmmanuele Bassi2022-02-131-0/+16
| | | | | It's pointless, as docbook's style sheets do not work any more, but gtk-doc still warns about them.
* Rename argument in the declationEmmanuele Bassi2022-02-131-1/+1
| | | | It must match the argument in the definition and the documentation.
* docs: Add missing symbols to the sections fileEmmanuele Bassi2022-02-131-0/+19
|
* Use GI_TYPE_TAG_IS_BASICEmmanuele Bassi2022-02-134-6/+6
| | | | Now that we have it.
* Add GI_TYPE_TAG_IS_BASICEmmanuele Bassi2022-02-131-1/+33
| | | | | And deprecate G_TYPE_TAG_IS_BASIC. Let's avoid hijacking the G namespace any further.
* docs: Rename a field annotationEmmanuele Bassi2022-02-131-1/+1
|
* docs: Reformat a long descriptionEmmanuele Bassi2022-02-131-0/+4
|
* docs: Remove DocBook tagsEmmanuele Bassi2022-02-1318-246/+117
| | | | | We are still using gtk-doc, but gtk-doc uses Markdown these days, not DocBook.
* Use the proper private triglyphEmmanuele Bassi2022-02-134-5/+4
| | | | It's `/*< ... >*/`, not `/* <...> */`.
* girffi: Add gi_type_tag_extract_ffi_return_value()Philip Chimento2022-02-132-26/+62
| | | | | | | | | | | | | | | | This new API does the same thing as gi_type_info_extract_ffi_return_value, but takes a GITypeTag instead of GITypeInfo pointer, and additionally a GIInfoType if the GITypeTag is GI_TYPE_TAG_INTERFACE. (These pieces of data are the only things used from the GITypeInfo structure.) It's intended for bindings using an argument cache, such as GJS and PyGObject, so that they don't have to store a whole 64-bit GITypeInfo pointer in their cache in many common cases, and can just store the 5-bit type tag instead, or the 5-bit interface type in case of GI_TYPE_TAG_INTERFACE. The original gi_type_info_extract_ffi_return_value() is reimplemented in terms of the new gi_type_tag_extract_ffi_return_value().
* girepository: Fix documentation commentsPhilip Chimento2022-02-131-4/+4
| | | | | It was driving me crazy that g_type_info_get_array_length() claimed to return an array length.
* girepository: Clarify SimpleTypeBlob documentationPhilip Chimento2022-02-131-3/+3
| | | | | | | The documentation comment for SimpleTypeBlob seemed to imply that a basic type was embedded if the reserved fields were nonzero. After examining the code, I believe that was actually due to some words missing, and the comment should say that the type is embedded if the fields are zero.
* gitypeinfo: Add GI_TYPE_TAG_IS_CONTAINER macroPhilip Chimento2022-02-132-4/+16
| | | | | Like GI_TYPE_TAG_IS_NUMERIC, this is a convenience for bindings that want to perform a similar action for all container types.
* gitypeinfo: Add GI_TYPE_TAG_IS_NUMERIC macroPhilip Chimento2022-02-132-2/+12
| | | | | | | | | | | | | | | | | | | | | This is a convenience for bindings that want to perform a similar action for all numeric types. It allows more expressive code in some cases: if (GI_TYPE_TAG_IS_NUMERIC(tag)) { do_one_thing(); return; } switch (tag) { case GI_TYPE_TAG_ARRAY: do_other_thing(); return; /* ... */ default: g_assert_not_reached(); } instead of listing out all of the numeric types in the switch statement.
* Revert "scanner: Mark colliding properties as not introspectable"Emmanuele Bassi2022-02-134-4/+36
| | | | | | | | | This reverts commit 8e85d1ca937c166f07675d02fc84abb27d06ae11. Marking colliding properties as not introspectable breaks a bunch of existing API when compiling the GIR into the typelib, so we'll have to find another solution during the grace period.
* Update glib introspection dataSebastian Dröge2022-02-122-2/+98
| | | | This is based on f9c08308ea0c25977b4e0153e868cb0a8703b75e
* Document the newly added g-ir-scanner CLI optionEmmanuele Bassi2022-02-122-0/+12
|
* Add --compiler argument to g-ir-scannerEmmanuele Bassi2022-02-123-5/+13
| | | | | | | | | | | | We currently use the `CC` environment variable to find the C compiler to use internally in g-ir-scanner. Build systems might wish to store the compiler detected during the build configuration, and then pass that compiler to g-ir-scanner at the time of build, avoiding to put things into the environment. One possible solution is to have a command line argument that lets us specify the C compiler, with the same semantics as the `CC` environment variable.
* scanner: Validate emitter methodsEmmanuele Bassi2022-02-121-0/+35
| | | | | | | | | Follow the same semantics as Vala: 1. emitters should have the same return value as the signal 2. emitters should have the same parameters as the signal they emit (minus the instance parameter, which is implied in signals)
* scanner: Add (emitter) annotation for signalsEmmanuele Bassi2022-02-127-10/+73
| | | | | | Signals that have an emitter function should have an annotation to allow consumers of the introspection XML to effectively pair signals to their corresponding emitter functions that share the same prototype.
* scanner: Fix strict log node emitterEmmanuele Bassi2022-02-121-1/+1
| | | | We need to use log_node(), not a plain log().
* scanner: Mark colliding properties as not introspectableEmmanuele Bassi2022-02-124-36/+4
| | | | | We prefer methods, signals, and virtual methods to properties, in case of a collision.
* scanner: Use strict_node() for property name collisionEmmanuele Bassi2022-02-121-1/+1
| | | | | This way we only raise a warning when operating under the newly added strict mode.
* scanner: Add strict modeEmmanuele Bassi2022-02-124-1/+32
| | | | | | | | | To avoid introducing additional strictness onto unsuspecting libraries, we introduce a new mode: "strict". The strict mode is opt-in, and used to signal potential issues with the public API once exposed by language bindings, even when it's fully introspectable.
* Handle property name collisionsEmmanuele Bassi2022-02-121-0/+41
| | | | | | | | | | | Properties cannot have the same name as signals, methods, and virtual functions, as they will break various language bindings. Since listing this requirement only in the documentation has been insufficient, we should emit a warning, and hope that library developers will pay attention to it. Fixes: #386
* Record: Properties are not supportedbadcel2022-02-101-2/+1
|
* Fix typos in commentsbadcel2022-02-091-4/+4
|
* Update glib introspection dataSebastian Dröge2022-02-033-11/+623
| | | | This is based on c7031164b13d1e184aeaf5850a10897b06269735
* Use binary mode buffer for stdout Hu Jialun2022-02-021-1/+1
| | | | | By default, stdout is in text mode, expecting a str rather than byte. Change the output destination to the underlying binary buffer to write bytes.
* CI: use a newer mypy in CI to fix the msys2 jobChristoph Reiter2022-02-023-6/+10
| | | | | | | | | | | | | MSYS2 recently updated Python to 3.9.10 which triggered a build issued present in typed_ast, which was fixed in typed_ast 1.5.0: https://github.com/python/typed_ast/issues/169 The currently used mypy version has an upper limit on typed_ast, so this fixed version wasn't pulled in. To fix this, update mypy, fix one new warning it complains about (namedtuple not being named after the variable), and install the markdown stubs explicitely, since mypy no longer bundles them.
* ci: ensure to use the downloaded pkg-config.exeAndoni Morales Alastruey2022-01-281-0/+2
|
* windows: fix build using subprojects with python >=3.8Andoni Morales Alastruey2022-01-282-10/+41
| | | | Fixes #416
* Update glib introspection dataSebastian Dröge2022-01-251-1/+1
| | | | This is based on 0ea10bf904e2098739fe0f5df52be549343effa9
* Update glib introspection dataSebastian Dröge2022-01-243-367/+793
| | | | This is based on d41282f7a85b0e1be61505ae85125a977a8ac557
* Add "forever" scope to docsbadcel2022-01-211-0/+1
|
* Add forever scopeMarcel Tiede2022-01-161-4/+4
|
* girepository: avoids segfault in case of bad gtypeLukas Oberhuber2022-01-121-1/+3
| | | | | | | If a <GType invalid> (that's the way it appears in python's debugger) is returned, `g_type_name` returns NULL. This function therefore returns NULL at this time as subsequent calls to `strlen( data->gtype_name)` segfault.
* gimarshallingtests: Add GValue round-trip and copy functionsMarco Trevisan (Treviño)2022-01-112-0/+35
| | | | | We can use them in Gjs to verify whether a value is properly packed and unpacked to GValue.
View Lorry Controller Status