summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Release 1.33.3GOBJECT_INTROSPECTION_1_33_3Colin Walters2012-06-261-1/+1
|
* Update glib annotations from gitRico Tzschichholz2012-06-232-6/+95
|
* scanner: complete the enum-to-error-quark fixGiovanni Campagna2012-06-185-2/+274
| | | | | | | | | | Turns out that the problem was not only in the wrong matching to GType enums, but also that the non-GType heuristics used to_underscores instead of to_underscores_noprefix, turning DBusError into D_Bus_Error instead of DBus_Error. Complete with various tests. https://bugzilla.gnome.org/show_bug.cgi?id=669350
* scanner: fix pairing of error quarks with registered enumsGiovanni Campagna2012-06-161-3/+5
| | | | | | | | | | _uscore_type_names maps from the c_symbol_prefix, which has the global ns prefix removed, so we need to split the function symbol before the lookup. Previously it worked because it used the heuristics for unregistered enums (and failed for GDBusError, which has two uppercase letters in succession) https://bugzilla.gnome.org/show_bug.cgi?id=669350
* Release 1.33.2GOBJECT_INTROSPECTION_1_33_2Colin Walters2012-06-051-1/+1
|
* Update annotations to glib 2.33.2Colin Walters2012-06-053-3/+46
|
* tests: Add marshalling test for a boxed struct propertyMartin Pitt2012-06-052-1/+19
| | | | | | | Also make the _copy()/_free() methods for GIMarshallingTestsBoxedStruct get along with NULL values. https://bugzilla.gnome.org/show_bug.cgi?id=676603
* tests: Add a refcounting boxedJasper St. Pierre2012-06-013-0/+60
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=677249
* tests: Add vfunc taking a caller-allocated out parameterMartin Pitt2012-06-012-0/+20
| | | | | This reproduces https://bugzilla.gnome.org/show_bug.cgi?id=653151
* tests: Add marshalling test for a caller-allocated out GValue parameterMartin Pitt2012-06-012-0/+12
| | | | | This came up as a side issue in https://bugzilla.gnome.org/show_bug.cgi?id=653151
* scanner: allow for functions that look like constructors but aren'tDan Winship2012-05-264-3/+28
| | | | | | | | | | | | If the scanner found a function with _new in its name, but not prefixed by the name of a known type, it would assume that the function was a constructor, and then complain that it couldn't figure out what it was a constructor for, and mark it introspectable=0. Instead, just assume that the function is not actually a constructor in that case (unless it's explicitly tagged as such). https://bugzilla.gnome.org/show_bug.cgi?id=676815
* givfuncinfo: Fix memory leakJasper St. Pierre2012-05-251-0/+1
| | | | The field info wasn't being freed after it was used
* tests: Fix a memory leakJasper St. Pierre2012-05-251-1/+4
| | | | | | | We need to unref the cairo surface here, as we are making the context be the sole owner of it. https://bugzilla.gnome.org/show_bug.cgi?id=671687
* tests: Add a foreign struct signal testJasper St. Pierre2012-05-254-1/+46
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=671687
* tests: Fix warningsJasper St. Pierre2012-05-251-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=671687
* Update annotationsJasper St. Pierre2012-05-241-0/+1613
|
* Update glib annotations from gitRico Tzschichholz2012-05-243-11/+99
|
* girepository: avoid crash when querying nonexistent infoPavel Holejsovsky2012-05-125-9/+28
| | | | | | | | | It appears that cmph library can return (n+1) when querying item not present in its original n-item-sized set. Adjust code so that it detects this condition and do not chase stray pointers resulting from this bogus(?) hash result. https://bugzilla.gnome.org/show_bug.cgi?id=675939
* GIMarshallingTests: Add GStrv propertyMartin Pitt2012-05-052-1/+14
|
* Fix regress_test_closure_variant return valueMartin Pitt2012-05-052-2/+4
| | | | | | | | | | | We need to g_variant_ref() the return type: the closure delivers it wrapped in a GValue, and the subsequent g_value_unset() unrefs it to zero otherwise. This was uncovered by the now working TestClosures.test_variant() test case in PyGObject. Also allow passing NULL as argument, to be able to test these code paths as well.
* Update glib annotations to 2.33.1Rico Tzschichholz2012-05-022-1471/+100
|
* Add the fixed width C99 types from stdint.hNeil Roberts2012-05-021-0/+9
| | | | | | | | | | | | | C99 has standard types for fixed width signed and unsigned integers. This adds types to giscanner to map them to the glib equivalent types. stdint.h also has other types to specify specify sizes with at least a certain number of bits, the fastest type with at least some number of bits, a type big enough to store a pointer and a type containing the most number of bits. These don't map well to glib types so I have ignored them. https://bugzilla.gnome.org/show_bug.cgi?id=674796
* Fix GVariant handling in regress_test_closure_variantMartin Pitt2012-05-022-5/+3
| | | | | | | | | | | Commit 7c4fbbd6 introduced some low-level g_memdup()ing of the passed GVariant in regress_test_closure_variant(). This causes a race condition with GI clients like pygobject's test suite, which sometimes fail with (runtests.py:15653): GLib-CRITICAL **: g_variant_ref_sink: assertion `value->ref_count > 0' failed Drop the memduping again, and instead make the argument non-const (which is true, as the method temporarily increases the refcount).
* g-ir-doc-tool: Update expected fileRico Tzschichholz2012-04-261-5/+5
| | | | Should have signal arguments in the right order
* Update glib annotations from gitRico Tzschichholz2012-04-262-5/+1630
|
* configure: Update to 1.33.0Rico Tzschichholz2012-04-261-1/+1
|
* tests: Add flags and enum to GValue GHash in/outMartin Pitt2012-04-241-0/+18
| | | | | | | Add a flag and enum check to the GHashes returned/expected by regress_test_ghash_gvalue_{return,in}(). https://bugzilla.gnome.org/show_bug.cgi?id=637466
* tests: Add array marshalling test for array without length argumentBastian Winkler2012-04-202-0/+16
| | | | | | | | | | | A test case with an array in-argument that is neither zero terminated, nor fixed length, nor blessed with a length argument. This is, for example, the case in clutter_texture_set_from_rgb_data() https://bugzilla.gnome.org/show_bug.cgi?id=674271 Signed-off-by: Martin Pitt <martinpitt@gnome.org>
* tests: Add GType property TestObj:gtypeBastian Winkler2012-04-193-1/+30
| | | | | | | | Needed for https://bugzilla.gnome.org/show_bug.cgi?id=674351 https://bugzilla.gnome.org/show_bug.cgi?id=674366 Signed-off-by: Martin Pitt <martinpitt@gnome.org>
* Update Gio/GLib/GObject annotationsStef Walter2012-04-182-68/+295
| | | | Ran misc/update-glib-annotations.py against current glib master.
* annotationparser: add test for comment lines not starting with ' * 'Dieter Verfaillie2012-04-171-0/+14
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=673806
* annotationparser: cleanup and add tests for the new warnings we now emitDieter Verfaillie2012-04-174-32/+214
| | | | | | | | | Including: - handle things in the logical order encountered (first colon, then annotations) - correctly report column when missing a colon on the identifier part - small type fixes - remove no longer useful "parameter/tag expected" warnings
* warningtester: make it possible to EXPECT multiple lines of outputDieter Verfaillie2012-04-171-60/+74
|
* Revert "annotationparser: indent _parse_comment_block gtkdoc code"Dieter Verfaillie2012-04-172-103/+95
| | | | | | | | | This reverts commit f41525d54f53edd9b0d665397f7c6c755ee3616b and adds a more complete solution as the original commit only handled empty lines between the GTK-Doc comment block start token "/**" and the identifier. https://bugzilla.gnome.org/show_bug.cgi?id=673806
* update-glib-annotations: Set required environment variablesColin Walters2012-04-171-0/+5
| | | | Assume srcdir=builddir, so users don't have to set this.
* annotationparser: indent _parse_comment_block gtkdoc codeAlban Browaeys2012-04-172-89/+98
| | | | | | | | | | | | | | | | | | | | The current logic in _parse_comment_block of the annotationparser check the identifier and use variables that only makes sense if a result was returned (column_offset, original_line). This patch indent the logic so it is only triggered if a result is found. Otherwise it returns None as expected by call chain "parse > parse_comment_block > _parse_comment_block": ie in "parse": comment_block = self.parse_comment_block(comment) if comment_block is not None: This still raises a lot of warnings but does not abort while generating gir for libgnomekbd, mutter or telepathy-glib (those thus have to be tweaked not to call g-ir-scanner with --warn-error at least until the parser mask those false positives or the doc from those projects is fixed to comply with the behaviour expected by giscanner). https://bugzilla.gnome.org/show_bug.cgi?id=673806
* Move libffi and gmodule to Requires.private in .pc filesKalev Lember2012-04-132-4/+8
| | | | | | | | | | | | | | | | | The intention of the change is to clean up unnecessary linking with libffi and gmodule in g-i consumers as they typically don't use any libffi/gmodule symbols. Listing libffi and gmodule in pkg-config Requires meant that every consumer that wanted to link with -lgirepository also got -lffi and -lgmodule-2.0, which caused ld to emit unnecessary DT_NEEDED entries. Moving the deps to Requires.private removes the internal dependencies from 'pkg-config --libs', but keeps them in --libs --static output. The change won't affect --cflags and the include directories necessary for <ffi.h> will still be listed. https://bugzilla.gnome.org/show_bug.cgi?id=674065
* Don't link with gthread-2.0Kalev Lember2012-04-134-4/+4
| | | | | | | Commit 2fff986 removed the use of g_thread_init() and we don't use any other symbols from gthread-2.0. https://bugzilla.gnome.org/show_bug.cgi?id=674065
* Make introspection compile with -Wall -WerrorJohan Dahlin2012-04-0916-12/+96
| | | | | Address all gcc warnings, -Werror is not enabled yet but at least -Wall -Werror passes on my machine.
* Compare filenames using g_file_equal()Johan Dahlin2012-04-093-3/+17
| | | | | | Makes it work on case-sensitive file systems such as HFS+. https://bugzilla.gnome.org/show_bug.cgi?id=667405
* Pass in LDFLAGS to the dumperJohan Dahlin2012-04-091-8/+9
| | | | | | | | We should honor LDFLAGS environment variable set by the user, so options such as -Wl,--enable-new-dtags properly get passed to the linker when creating the dumper binary https://bugzilla.gnome.org/show_bug.cgi?id=670152
* annotationparser: split validate() into sub-methodsWill Thompson2012-04-091-58/+67
| | | | | | | | Most cases in validate() were already simply calls to _validate_option() with particular arguments; this extracts the code from the remaining options to their own methods, making the dispatch table more legible. https://bugzilla.gnome.org/show_bug.cgi?id=670985
* annotationparser: correct "maximium" in error messagesWill Thompson2012-04-093-5/+5
| | | | | | | | "Maximium" is not an English word. Even if corrected to "maximum" (which is), "at maximum" is not conventional usage: "at most" is more idiomatic. https://bugzilla.gnome.org/show_bug.cgi?id=670985
* annotationparser: remove duplication of annotation namesWill Thompson2012-04-091-13/+13
| | | | | | | | | | Previously, the validation code compared each option name to a constant (such as OPT_ALLOW_NONE) which expands to the string used in a source file, and if they matched it would typically pass that same string to _validate_option(). But the annotation name was written out longhand each time, which seemed strange to me. https://bugzilla.gnome.org/show_bug.cgi?id=670985
* giscanner: Don't run pkg-config when there's no packages specifiedJasper St. Pierre2012-04-091-3/+4
| | | | | | | This prevents a simple error from pkg-config, "Must specify package names on command line" https://bugzilla.gnome.org/show_bug.cgi?id=673668
* Avoid _get_func() consuming reference from input infoPavel Holejsovsky2012-04-072-2/+14
| | | | | | | | | | | | Fix of leak in 4c9424e18d71237f438a99bc5f2d45ae7de60b78 was a bit overaggressive, stealing also one reference from input 'info' argument. Also fixes another bug in that commit - local 'func' shadowing the return value, causing that function always returned NULL even when some result was actually found. https://bugzilla.gnome.org/show_bug.cgi?id=673282
* Split parameter and tag storage in annotationparser parse treeDieter Verfaillie2012-04-056-45/+90
| | | | | | | | | | | This avoids tags overwriting parameters if they happen to share the same name. For example, this was triggered by valid code in libgnome-keyring. tests/scanner/regress.c and tests/scanner/regress.h test written by Colin Walters <walters@verbum.org>. https://bugzilla.gnome.org/show_bug.cgi?id=672254
* Don't extract annotations from headersJohan Dahlin2012-04-051-16/+0
| | | | | | The headers are already parsed as they are passed in to g-ir-scanner. This avoids quite a few warnings triggered with the new annotation parser.
* Update annotations from git.Johan Dahlin2012-04-053-21422/+10
| | | | | This removes also all the headers as it's the first run with the updated extraction tool.
* Do the filename filtering in scannerlexerJohan Dahlin2012-04-052-8/+18
| | | | | This avoids a bit of python work and reduces the amount of allocations.
View Lorry Controller Status