summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Make gtk-doc not a hard dependency of gobject-introspectionbaserock/morphJavier Jardón2013-03-043-5/+18
| | | | Fixes https://bugzilla.gnome.org/show_bug.cgi?id=684795
* gir.morph: use PREFIXRichard Maw2013-03-041-1/+1
|
* gir: add morphRichard Maw2013-03-041-0/+8
| | | | | --disable-tests is needed, otherwise configure fails because cairo is needed for the tests and it is a gratuitous dependency
* Update glib annotations to 2.34.2gnome-3-6Martin Pitt2012-11-132-26/+29
|
* Release 1.34.2GOBJECT_INTROSPECTION_1_34_2Colin Walters2012-11-121-2/+2
|
* scanner: Correctly handle large 64 bit integer constantsColin Walters2012-11-125-6/+34
| | | | | | | | | | | | | | | | | | | | 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
* gimarshallingtests: Fix return data typeMartin Pitt2012-11-092-2/+2
| | | | | | 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().
* Release 1.34.1.1GOBJECT_INTROSPECTION_1_34_1_1Colin Walters2012-10-171-1/+3
|
* [gobject-introspection] Add test method for GDestroy with no user dataSimon Feltman2012-10-173-0/+36
| | | | | | | Added regress_test_callback_destroy_notify_no_user_data. Updated Regress-1.0-expected.gir https://bugzilla.gnome.org/show_bug.cgi?id=685922
* Release 1.34.1GOBJECT_INTROSPECTION_1_34_1Colin Walters2012-10-171-1/+1
|
* build: Require GLib 2.34.1Colin Walters2012-10-171-1/+1
|
* Update glib annotations to 2.34.1Rico Tzschichholz2012-10-171-1/+1
|
* gimarshallingtests: Add array/GList uint32/64 in/out APIMartin Pitt2012-10-112-0/+68
| | | | | | | | 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
* Release 1.34.0GOBJECT_INTROSPECTION_1_34_0Colin Walters2012-09-241-2/+2
|
* Update annotations to glib 2.34.0Rico Tzschichholz2012-09-243-18/+36
|
* configure: Post-release version bumpColin Walters2012-09-181-1/+1
|
* Release 1.33.14GOBJECT_INTROSPECTION_1_33_14Colin Walters2012-09-181-1/+1
|
* Update annotations from glib gitRico Tzschichholz2012-09-171-0/+14
|
* regress: Add API to test signals with (u)int64 paramsNicolas Dufresne2012-09-123-0/+102
| | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=683596 Co-Authored-By: Martin Pitt <martinpitt@gnome.org>
* Update annotations from glib gitMartin Pitt2012-09-111-2/+2
|
* gimarshallingtests: Add in/out int64 GValue method argumentsMartin Pitt2012-09-102-0/+30
| | | | See https://bugzilla.gnome.org/show_bug.cgi?id=683596
* GLib-2.0.gir: Add glib-unix.hColin Walters2012-09-051-0/+3
| | | | So we pick up g_unix_signal_add() for example.
* Update annotations from glib gitGOBJECT_INTROSPECTION_1_33_10Rico Tzschichholz2012-09-033-736/+1185
|
* ginvoke: support conversion of fundamental type GParamSpec valuesMark Nauwelaerts2012-09-031-0/+5
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=683265
* Update tests to show off some new featuresJasper St. Pierre2012-08-294-17/+86
| | | | These includes more proper links and fundamentals.
* mallardwriter: Fix fundamental false alarms for the C formatterJasper St. Pierre2012-08-291-13/+13
| | | | | Just use a constant translation dictionary. If somebody needs something more fancy they can use a custom match.
* mallardwriter: Fix formatting the function nameJasper St. Pierre2012-08-292-3/+3
| | | | This is not what format_type is for.
* girparser: Track methods/constructors by symbolJasper St. Pierre2012-08-292-13/+22
| | | | | | | 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
* ast: Remove what looks to be a copy/paste errorJasper St. Pierre2012-08-291-2/+0
| | | | | | | | 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
* .gitignore: Add doctool examples outputJasper St. Pierre2012-08-291-0/+2
|
* tests: Don't error out if there is no existing directoryJasper St. Pierre2012-08-291-2/+2
|
* mallardwriter: Remove some silly codeJasper St. Pierre2012-08-291-2/+1
| | | | This silly code was part of a debugging harness.
* mallardwriter: Fix whitespaceJasper St. Pierre2012-08-291-1/+1
| | | | | The whitespace should come included with the surrounding 'other' tokens. We shouldn't need to add any.
* mallardwriter: Fix property and signal outputJasper St. Pierre2012-08-291-4/+10
|
* giscanner: Fix make check issuesJasper St. Pierre2012-08-292-12/+14
| | | | Whoops.
* mallardwriter: Hack a lot more on document block processingJasper St. Pierre2012-08-291-82/+214
| | | | | Use a new regex scanner to parse the contents of document blocks and emit the proper XML document for it.
* mallardwriter: Remove a silly try/exceptJasper St. Pierre2012-08-291-4/+1
| | | | This isn't necessary as far as I can tell
* mallardwriter: Use a more generic system for language formattingJasper St. Pierre2012-08-291-7/+16
|
* mallardwriter: Remove some unused stuffJasper St. Pierre2012-08-281-6/+0
|
* docmain: Fix error messageJasper St. Pierre2012-08-281-1/+1
|
* girepository: Fix leak in g_vfunc_info_get_addressJasper St. Pierre2012-08-251-3/+7
| | | | | | We need to fix the struct info here. https://bugzilla.gnome.org/show_bug.cgi?id=682647
* girepository: Add g_interface_info_find_signalTorsten Schönfeld2012-08-253-0/+36
| | | | | | | Add the convenience method g_interface_info_find_signal, mirroring g_object_info_find_signal. https://bugzilla.gnome.org/show_bug.cgi?id=682672
* scanner: methods cannot have an out-arg as their first argTorsten Schönfeld2012-08-214-0/+57
| | | | | | | | | | | | 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
* Post-release version bumpColin Walters2012-08-201-1/+1
|
* gimarshallingtests: Add GParamSpec return and (out) argumentMathieu Duponchelle2012-08-202-0/+25
| | | | | | https://bugzilla.gnome.org/show_bug.cgi?id=681565 Co-Authored-By: Martin Pitt <martinpitt@gnome.org>
* girffi: Fix g_callable_info_prepare_closure for certain callablesJasper St. Pierre2012-08-201-71/+44
| | | | | | | | 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
* gicallableinfo: Add two new convenience methods: is_method and can_throw_gerrorJasper St. Pierre2012-08-203-27/+74
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=673805
* Release 1.33.9GOBJECT_INTROSPECTION_1_33_9Colin Walters2012-08-201-1/+1
|
* Update annotations from glib gitColin Walters2012-08-202-74/+259
|
* Makefile.introspection: Add gir dependency to exampleColin Walters2012-08-141-0/+1
|