| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=641347
|
|
|
|
| |
The cairo/ directory is searched for header files anyway.
|
|
|
|
|
|
| |
So methods such as gtk_drag_dest_set() can be put inside Gtk.Widget
https://bugzilla.gnome.org/show_bug.cgi?id=639945
|
|
|
|
|
| |
Preserve the section names and write them out on the class/record/
interface.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=561264
|
|
|
|
|
|
| |
So the element type has the correct is_pointer flag
https://bugzilla.gnome.org/show_bug.cgi?id=638929
|
|
|
|
|
|
|
|
|
|
|
|
| |
Scanner tries to detect caller-allocates attribute automatically if
not explicitly specified by checking that parameter is not double-referenced
and is struct or union. This patch adds resolving of aliases when
checking whether parameter is struct or union.
Also removes old incorrect method transformer.follow_aliases, which
was never used in current code.
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=639081
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=634838
|
| |
|
| |
|
|
|
|
|
|
|
| |
* don't skip those associated to a signal
* don't warn if it doesn't have an invoker
https://bugzilla.gnome.org/show_bug.cgi?id=637215
|
| |
|
|
|
|
|
| |
* Fix use of tabs
* Update for correct signal parameters
|
|
|
|
|
|
|
|
|
|
|
| |
Inside an alias definition, we only need the name of the alias target
type. Add a method to GIRWriter to write out a type reference rather
than full type definition and use it when writing out an alias.
Determine introspectableness of aliases in IntrospectablePass so functions
using aliases can be marked not-introspectable if the alias itself is not.
https://bugzilla.gnome.org/show_bug.cgi?id=629682
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If present in annotation, use parameter names from annotation instead
of (object, p0, p1, ...) names generated by dumpparser.
Assign names for all parameters before trying to resolve annotation
types, so that annotations containing forward references to other
arguments, e.g.
* GApplication::open:
* @application: the application
* @files: (array length=n_files) (element-type GFile): an array of #GFiles
* @n_files: the length of @files
|
|
|
|
|
|
|
|
|
| |
regress_test_fundamental_sub_object_finalize should call parent's
regress_test_fundamental_object_finalize instead of
regress_test_fundamental_object_unref, otherwise recursion and
double-free might happen.
https://bugzilla.gnome.org/show_bug.cgi?id=636620
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Modify the lexer to consider all "trigraph" comments specially, and
parse them for "flags" as well as "private" and "public" (which were
previously hardcoded). This change allows for future support of
multiple annotations inside a single trigraph comment.
- Change the parser to consider the additional field "flags" set by
the lexer when constructing enums.
- Add a test case for the "flags" trigraph comment to the scanner
annotation tests.
See <https://bugzilla.gnome.org/show_bug.cgi?id=631530>.
|
|
|
|
|
|
|
| |
g_strcompress() only does some of what we need; fork it
and add support for \x escapes too.
https://bugzilla.gnome.org/show_bug.cgi?id=595773
|
|
|
|
|
|
|
|
| |
These are the only things for which we expect native values to be
preserved; for e.g. flags and integers, we expect bindings to convert.
The particular rationale for this patch is to avoid flagging flags (sic)
as (out caller-allocates).
|
|
|
|
|
|
|
|
|
| |
If we have a C symbol prefix for the target type, then use that to
identify methods that should be paired with it. The C symbol prefix
is derived from the name of the _get_type() function, so it's likely
that this is also the prefix given to methods for the type.
https://bugzilla.gnome.org/show_bug.cgi?id=634153
|
|
|
|
|
|
|
| |
Some API such as gtk_text_iter_get_char returns an individual
"gunichar"; we should support this.
https://bugzilla.gnome.org/show_bug.cgi?id=633197
|
|
|
|
|
| |
This is cleaner and faster, and prepares us better for an incoming
import of CMPH.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The C compiler will pick an enumeration type that accomodates the specified
values for the enumeration, so ignoring 64-bit enumerations, we can
have enumeration values from MININT32 to MAXUINT32. To handle this properly:
- Use gint64 for holding eumeration values when scanning
- Add a 'unsigned_value' bit to ValueBlob so we can distinguish the
int32 vs. uint32 cases in the typelib
- Change the return value of g_value_info_get_value() to gint64.
https://bugzilla.gnome.org/show_bug.cgi?id=629704
|
| |
|
|
|
|
|
|
| |
Might as well be liberal here, as long as we have a test case.
https://bugzilla.gnome.org/show_bug.cgi?id=631690
|
|
|
|
| |
This reverts commit d15e386c8e10dd6b645a444e29cc053100089a07.
|
|
|
|
| |
Previously, such annotations would be ignored.
|
| |
|
|
|
|
|
|
|
|
| |
The annotation parser changed to be stricter about annotation content,
but we introduced a regression where a : in the documentation would
wrongly cause the annotation to be skipped.
https://bugzilla.gnome.org/show_bug.cgi?id=630862
|
|
|
|
|
|
| |
... because for 'in' arguments only (transfer none) is correct.
https://bugzilla.gnome.org/show_bug.cgi?id=630788
|
|
|
|
|
|
|
| |
Declaring input parameters with transfer other than none is
discouraged, so don't do it in the testsuite.
https://bugzilla.gnome.org/show_bug.cgi?id=630788
|
|
|
|
|
| |
We don't want people making functions which take ownership of
arguments, so don't do it in the test suite.
|
|
|
|
| |
This is a follow-up to 60a8c75 which wasn't properly fixed.
|
|
|
|
|
| |
Allow closures without annotations to avoid having
to duplicate the parameter name.
|
| |
|
|
|
|
|
|
| |
Warn for invalid annotations.
Change so that custom attributes have to use the annotation
keyword.
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=594125
|
|
|
|
|
|
|
| |
For that we also need to read the annotations for foreign structs
before guessing the transfer mode of return values.
https://bugzilla.gnome.org/show_bug.cgi?id=629188
|
|
|
|
|
|
|
| |
We weren't doing this consistently, which broke nsname != cprefix
cases.
https://bugzilla.gnome.org/show_bug.cgi?id=629683
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=629359
|
|
|
|
|
|
|
|
| |
* Explicitly check for ast.Alias in annotation pass
* Add "generic" attribs handling for aliases like docs, introspectable=0
etc.
https://bugzilla.gnome.org/show_bug.cgi?id=629668
|
|
|
|
|
| |
Our Type creation from GType names didn't know how to handle
the GObject boxeds for GHashTable, GArray etc.
|
|
|
|
|
|
|
|
| |
The "c_name" is really a fallback; use "ctype" if available which
matches the C structure name.
This fixes scanning at least TelepathyGLib where the namespace is
different from the C prefix "Tp".
|
|
|
|
| |
Similar to TelepathyGlib.
|
|
|
|
| |
Instead use xxxdir + xxx_DATA which uninstalls correctly
|
| |
|
|
|
|
|
| |
Multiple modules have '_' prefixed symbols in "public" headers
meaning "don't use this in your app".
|
|
|
|
|
| |
Typically these contain reserved callbacks; in any case we take
a leading underscore to mean 'private'.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was a stupid abstraction split, we only support GObject.
* Clean up how we handle c:type - we only set it if we've actually
seen a corresponding structure.
* Add a warning if we don't see the structure typedef for an
interface, since that's pretty bogus. (And fix regress.h to have
one)
* Rename the "type_name" attribute internally to "gtype_name"
for clarity.
|