| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We didn't have good coverage of say in arguments after out.
https://bugzilla.gnome.org/show_bug.cgi?id=611809
|
|
|
|
| |
Useful to debug case https://bugzilla.gnome.org/show_bug.cgi?id=611529
|
|
|
|
|
| |
Instead of catching all errors, including AttributeError,
TypeError and NameError.
|
|
|
|
|
|
| |
If we don't have permission to execute the libtool binary, we'd
just throw here which is wrong. Fix this by catching all
exceptions.
|
|
|
|
|
|
|
|
|
|
|
|
| |
The enumeration type for an error might not be introspected
and registered with GObject (this is, in particular, true for
the errors in GLib itself). So, as a fallback search, through
all enum types in the module.
Add a special case for the aberrant GIOErrorEnum and a warning
if resolution completely fails.
https://bugzilla.gnome.org/show_bug.cgi?id=602512
|
|
|
|
| |
Colin should remember to run `make check' before comitting!
|
|
|
|
|
| |
If g_alloca failed we're pretty much screwed, and g_return_if_fail
is for API entry points, not internal assertions.
|
|
|
|
|
|
|
| |
All GCancellables are allow-none, this allows us to remove a lot
of custom annotations.
https://bugzilla.gnome.org/show_bug.cgi?id=604658
|
|
|
|
|
|
| |
Signed-off-by: Kedar Sovani <kedars@marvell.com>
https://bugzilla.gnome.org/show_bug.cgi?id=606139
|
|
|
|
|
|
| |
To make things really better we should track the line origin of
element from the .gir file (and actually we need to do better
checking in the scanner), but this is slightly less lame.
|
| |
|
|
|
|
| |
We should avoid exceptions being propagated to the toplevel.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=608724
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=608723
|
|
|
|
| |
New limit is 0x7FFFFFFF.
|
|
|
|
|
| |
following my previous patch to systematically specify the scope in
callbacks. Had forgotten to add these.
|
|
|
|
|
|
| |
default to 'call' as stated in the annotation documentation.
https://bugzilla.gnome.org/show_bug.cgi?id=607026
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When looking at an embedded type (e.g. a Callback after a Field), the
offset we put in the info structure was to the CallbackBlob itself.
However the code in g_type_info_get_interface assumed that the offset
was to a SimpleTypeBlob, which it wasn't.
https://bugzilla.gnome.org/show_bug.cgi?id=606180
|
|
|
|
|
|
|
|
|
| |
We're going to remove the entire temporary directory,
so there's no point in explicitly removing just the .c file
we create; leaving the .c file behind makes it easier to debug
problems.
https://bugzilla.gnome.org/show_bug.cgi?id=605966
|
| |
|
|
|
|
|
|
|
|
|
|
| |
One might need to call some init functions before being able to call
get_type() to create the types of a library.
--add-init-section let the user insert some initialization code in the
introspection program.
https://bugzilla.gnome.org/show_bug.cgi?id=605778
|
|
|
|
| |
Not in the public girffi.h.
|
|
|
|
|
|
|
|
|
|
|
|
| |
glib uses __extension__ in macros dealing with 64 bits integer such as
GUINT64_SWAP_LE_BE().
To quote the GCC manual:
`-pedantic' and other options cause warnings for many GNU C extensions. You
can prevent such warnings within one expression by writing `__extension__'
before the expression.
https://bugzilla.gnome.org/show_bug.cgi?id=605779
|
|
|
|
|
|
|
| |
--no-libtool means that one does not want to use libtool to compile the
introspection program.
https://bugzilla.gnome.org/show_bug.cgi?id=605774
|
|
|
|
| |
Also make sure to add cflags from gio-unix-2.0 to avoid a warning
|
| |
|
|
|
|
| |
This avoids pyconfig.h:1028:1: warning: "_POSIX_C_SOURCE" redefined
|
|
|
|
| |
Also suppress a bit more using @
|
|
|
|
|
| |
We should not require AM_DEFAULT_VERBOSITY to be present, workaround
that fact
|
|
|
|
|
| |
This is only supported with automake 1.11 or newer, older versions
should default to showing nothing for now.
|
|
|
|
|
|
|
| |
Otherwise, suncc reports error when parsing /usr/include/glib-2.0/glib/ghostutils.h,
and stops parsing rest headers.
https://bugzilla.gnome.org/show_bug.cgi?id=605108
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We don't want to malloc each GIBaseInfo when they can be used in
function invocation; instead, allow stack allocation.
There were a lot of structure typedefs which were actually just
exactly the same as GIBaseInfo, with the one exception of GITypeInfo.
Instead, just put the single GITypeInfo boolean inside GIBaseInfo
as a bit in a bitfield.
GIBaseInfo is still opaque publicly; GIRealInfo is the new
internal structure.
Using this, add new functions to retrieve arguments and argument types
on the stack.
https://bugzilla.gnome.org/show_bug.cgi?id=604074
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than having bindings use g_function_info_invoke, which is basically
a toy/demo API, export a convenience utility function which takes the introspection
information and sets up things we need to pass to libffi.
Then invocation can be done directly to libffi by a binding.
As part of this work, remove some (unused by gjs) public functions from the
girffi API, and instead export a function to map to libffi which can work
semi-correctly.
https://bugzilla.gnome.org/show_bug.cgi?id=604074
|
| |
|
| |
|
|
|
|
|
|
|
| |
glib-compat.h file created to use g_mapped_file_unref only if
glib >= 2.22 is available
https://bugzilla.gnome.org/show_bug.cgi?id=603727
|
|
|
|
|
|
| |
retval should be a valid pointer
https://bugzilla.gnome.org/show_bug.cgi?id=604472
|
|
|
|
|
|
| |
ffi_call does not protect against retval being NULL, resulting in a segfault.
https://bugzilla.gnome.org/show_bug.cgi?id=604472
|
|
|
|
| |
This reverts commit 28cccba737ec2214da66b0d74059278162cf5fd0.
|
|
|
|
|
| |
It's useful to be able to include the makefile without
having introspection enabled.
|
| |
|
|
|
|
| |
Also, make sure that it is included in the dist
|
|
|
|
|
| |
As it breaks when including the makefile when using
an absolute path.
|
|
|
|
|
| |
This will make it easier for third-party projects to use
introspection by having easy make rules.
|
| |
|
|
|
|
|
|
|
| |
acts as a regression test on the recognizing-GLib.List-inside-glib
part of the previous patch.
https://bugzilla.gnome.org/show_bug.cgi?id=602512
|