| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In C, positive integer constants are by default unsigned. This means
an expression like 0x8000000000000000 will be "unsigned long long".
In the actual scanner code, we were parsing them as "gint64", and
storing them as gint64. This was incorrect; we need to parse them
as guint64, and store the bits we get from that. This gives us
an equivalent result to what the C compiler does.
However, when we actually return the value as a Python "long"
(arbitrary length integer), we need to treat the value as unsigned if
the result indicated it was.
https://bugzilla.gnome.org/show_bug.cgi?id=685022
Conflicts:
tests/scanner/Regress-1.0-expected.gir
tests/scanner/regress.h
|
|
|
|
|
|
| |
gi_marshalling_tests_genum_returnv() should (and does) return a
GIMarshallingTestsGEnum, not a GIMarshallingTestsEnum. The latter is already
covered by gi_marshalling_tests_enum_returnv().
|
| |
|
|
|
|
|
|
|
| |
Added regress_test_callback_destroy_notify_no_user_data.
Updated Regress-1.0-expected.gir
https://bugzilla.gnome.org/show_bug.cgi?id=685922
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Add in/out API for testing arrays containing uint64, as well as GList
containing uint32 (GList and GHash can't contain 64 bit values as they store
them in pointers).
https://bugzilla.gnome.org/show_bug.cgi?id=685860
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=683596
Co-Authored-By: Martin Pitt <martinpitt@gnome.org>
|
| |
|
|
|
|
| |
See https://bugzilla.gnome.org/show_bug.cgi?id=683596
|
|
|
|
| |
So we pick up g_unix_signal_add() for example.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=683265
|
|
|
|
| |
These includes more proper links and fundamentals.
|
|
|
|
|
| |
Just use a constant translation dictionary. If somebody needs something
more fancy they can use a custom match.
|
|
|
|
| |
This is not what format_type is for.
|
|
|
|
|
|
|
| |
In order to be able to linkify a constructor/method, we need
to first track it by symbol.
https://bugzilla.gnome.org/show_bug.cgi?id=682969
|
|
|
|
|
|
|
|
| |
A symbol isn't a ctype. None of the tests failed when I removed
this, git blame wasn't very enlightening, and we don't remove this
in the remove method, so I'm thinking it's an error.
https://bugzilla.gnome.org/show_bug.cgi?id=682969
|
| |
|
| |
|
|
|
|
| |
This silly code was part of a debugging harness.
|
|
|
|
|
| |
The whitespace should come included with the surrounding 'other'
tokens. We shouldn't need to add any.
|
| |
|
|
|
|
| |
Whoops.
|
|
|
|
|
| |
Use a new regex scanner to parse the contents of document blocks
and emit the proper XML document for it.
|
|
|
|
| |
This isn't necessary as far as I can tell
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We need to fix the struct info here.
https://bugzilla.gnome.org/show_bug.cgi?id=682647
|
|
|
|
|
|
|
| |
Add the convenience method g_interface_info_find_signal, mirroring
g_object_info_find_signal.
https://bugzilla.gnome.org/show_bug.cgi?id=682672
|
|
|
|
|
|
|
|
|
|
|
|
| |
This ensures that if the first argument of a function like
gboolean gdk_rgba_parse (GdkRGBA *rgba, const gchar *spec);
is annotated as being an out-arg, the result is a class function with two
arguments, not a method with one argument. Previously, the (out) annotation
was simply ignored.
https://bugzilla.gnome.org/show_bug.cgi?id=682124
|
| |
|
|
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=681565
Co-Authored-By: Martin Pitt <martinpitt@gnome.org>
|
|
|
|
|
|
|
|
| |
Namely, those that are methods and those that throw GErrors.
We have very similar code in two places that calculate arg lengths and
argument types to stick into libffi. Merge, clean up, and correct both.
https://bugzilla.gnome.org/show_bug.cgi?id=673805
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=673805
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We were conditionalizing on the presence of cairo in the buildroot,
but that's super lame since it makes a huge mess of the build
dependency graph.
Let's just always stick cairo-gobject in there. I doubt anyone cares
anymore about building g-i on really old systems without it.
If they do...well, we can revisit this again.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 764366f7e4ef5a765a24ffac8c60b811f38b9ad9.
It can't work right now because to really use the structures, you need
to register them as a boxed, and that means we also need to rename the
boxed type.
A future version of this patch will need to handle both the structure
name and the GType name.
https://bugzilla.gnome.org/show_bug.cgi?id=675985
|
|
|
|
| |
Previous commit used old-style declarations which was broken.
|