diff options
author | Christoph Reiter <reiter.christoph@gmail.com> | 2015-01-08 21:31:20 +0100 |
---|---|---|
committer | Christoph Reiter <creiter@src.gnome.org> | 2017-05-17 23:03:00 +0200 |
commit | 12c304562add775dd80f698ad23aa59e8e87d879 (patch) | |
tree | ceed552d1a130b0335d498ffd55ba79c712fb24e /tests/scanner/Regress-1.0-Python-expected/Regress.AnnotationObject.out.page | |
parent | 3a140df2d29410d91f9bc86e9dd8bfbf82b3fad3 (diff) | |
download | gobject-introspection-12c304562add775dd80f698ad23aa59e8e87d879.tar.gz |
Add a test for "(in) (transfer floating)" parameters beeing an alias for "(in) (transfer none)".
The "(in)" alias was (unintenionally?) introduced in
https://git.gnome.org/browse/gobject-introspection/commit/?id=699ad0fec427c79bec1
which added an alias for return annotations. This change makes sure that this continues
to work.
Functions which ref_sink in params are currently marked as transfer-none since in the
case of non-floating objects (which all bindings use) no ownership gets transfered.
But in case of floating objects, which is the common case when using the C API directly,
the ownership _is_ transfered. Using transfer-floating should make this clearer
while giving the same result for bindings.
Functions where this could be used: gst_bin_add, gtk_container_add, gst_element_add_pad
See https://bugzilla.gnome.org/show_bug.cgi?id=657202 and https://bugzilla.gnome.org/show_bug.cgi?id=702960
https://bugzilla.gnome.org/show_bug.cgi?id=742618
Diffstat (limited to 'tests/scanner/Regress-1.0-Python-expected/Regress.AnnotationObject.out.page')
0 files changed, 0 insertions, 0 deletions