summaryrefslogtreecommitdiff
path: root/tests/gimarshallingtests.h
Commit message (Collapse)AuthorAgeFilesLines
* gimarshallingtests.h: Remove unimplemented functionsGOBJECT_INTROSPECTION_1_29_17Colin Walters2011-08-291-4/+0
| | | | The new missing-element-type warning triggers for these.
* Forbid GPtrArrays holding non-pointer typesGiovanni Campagna2011-08-181-2/+0
| | | | | | | | | It should be safe for bindings to assume that GPtrArrays hold only pointers (or values as big as it), so there is no need to go through hoops for converting smaller integers when marshalling. Libraries that need arrays of integers should use GArray. https://bugzilla.gnome.org/show_bug.cgi?id=652753
* Added marshalling tests for GPtrArrayAlex Eftimie2011-06-171-0/+17
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=652256
* gimarshallingtests: Add a test function that looks like gtk_init()Colin Walters2011-06-161-0/+2
|
* gimarshallingtests: Remove gi_marshalling_tests_array_nested_inColin Walters2011-06-161-1/+0
| | | | We don't actually support nested container types in practice.
* Add tests for complex arrays as in argumentsGOBJECT_INTROSPECTION_1_29_0Giovanni Campagna2011-06-131-93/+99
| | | | | | | Previously gjs supported only arrays of integers. Now that this changed, we need tests to avoid regressions. https://bugzilla.gnome.org/show_bug.cgi?id=646632
* gimarshallingtests: add a few more array testsDan Winship2011-06-101-0/+3
| | | | | | | | Add some tests with parameters on either side of an out array length parameter, to ensure that bindings that omit the length parameter don't mess up any other parameters. https://bugzilla.gnome.org/show_bug.cgi?id=651558
* Add tests for returning zero-terminated arrays of non-stringsGiovanni Campagna2011-05-121-2/+4
| | | | | | | gjs has always supported zero-terminated arrays of strings, and nothing else. Now that this changed, we need to test it. https://bugzilla.gnome.org/show_bug.cgi?id=634253
* [tests] add a gclosure_return method to test passing GClosures between methodsJohn (J5) Palmieri2011-03-161-1/+1
|
* Add GIMarshalllingTests function with in parameter as well as GError.Laszlo Pandy2011-02-231-0/+1
| | | | | This allows bindings to test the ability to clean up (in) parameters after a GError is set by the wrapped function.
* Add mask flags to GIMarshallingTests to test for flags with the same value.Laszlo Pandy2011-02-231-2/+8
| | | | | | | Glib uses flag aliases, multiple flag names with the same int value. For example G_IO_FLAG_MASK and G_IO_FLAG_GET_MASK. We need these flag values to test that gi bindings don't assume that all flags have the same value.
* Add non GType flags to GIMarshallingTests.Laszlo Pandy2011-02-221-0/+18
|
* [tests] Add GIMarshallingTests function for multiple in and multiple out args.Laszlo Pandy2011-02-181-2/+2
|
* Add GIMarshallingTests.Interface2Tomeu Vizoso2011-01-201-0/+23
| | | | | so we can test conflicts when two bases have a vfunc with the same name.
* Add GIMarshallingTests function which sets a GError, to test exception ↵Laszlo Pandy2011-01-191-0/+8
| | | | | | handling in bindings. https://bugzilla.gnome.org/show_bug.cgi?id=639834
* [tests] add tests for guint8 arraysIgnacio Casal Quinteiro2011-01-191-0/+2
| | | | | | * guint8 can be interpreted as array characters that can be memcpyied during marshalling so add a test to check if we are correctly handling this codepath
* Add a second enum to GIMarshallingTests to support pygi tests for non-gtype ↵Laszlo Pandy2011-01-171-0/+6
| | | | | | | | enums. There was a bug in pygi in which non-gtype enums shared values between themselves. That is, if there was an attribute Enum.THE_VALUE, it would be available on as OtherEnum.THE_VALUE as well. To make a test case for this bug, we need a second non-gtype enum in GIMarshallingTests to compare with.
* test: gi_marshalling_tests_array_gvariant_inMikkel Kamstrup Erlandsen2011-01-171-0/+2
| | | | | | A new test to expose a bug in pygobject https://bugzilla.gnome.org/show_bug.cgi?id=638915
* gimarshallingtests: Fix (inout) test cases, drop unsupported APIColin Walters2010-08-311-40/+29
| | | | | | | | | | | First, (inout) doesn't mean "mutates the argument". It means "I take an input argument here, and will also return a *new* argument in this position." C API which mutates e.g. structures is just unannotated. Mutation of containers like GList, GHashTable is simply disallowed. Secondly, we can't support C API which returns non-boxed structures with a transfer other than (none). The scanner will warn about this in the future.
* tests: Readd gimarshallingtests.[ch]Colin Walters2010-08-311-0/+736
For backwards compatibility with tests, for now resurrect these test cases (also, fix the namespacing on them while we're here). Like Everything, these get installed in source form.
View Lorry Controller Status