After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 745336 - Should regress_test_array_int_inout free the given list?
Should regress_test_array_int_inout free the given list?
Status: RESOLVED OBSOLETE
Product: gobject-introspection
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gobject-introspection Maintainer(s)
gobject-introspection Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-02-28 16:26 UTC by Torsten Schoenfeld
Modified: 2018-02-08 12:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Torsten Schoenfeld 2015-02-28 16:26:55 UTC 
Given these annotations:

/**
 * regress_test_array_int_inout:
 * @n_ints: (inout): the length of @ints
 * @ints: (inout) (array length=n_ints) (transfer full): ...
 */
void
regress_test_array_int_inout (int *n_ints, int **ints)

I expect regress_test_array_int_inout to free *ints prior to overwriting it.  But it doesn't.  Should it?
Comment 1 Torsten Schoenfeld 2015-02-28 17:21:16 UTC 
Similarly, shouldn't gi_marshalling_tests_garray_utf8_full_inout and gi_marshalling_tests_gptrarray_utf8_full_inout free the elements of the given arrays?

/**
 * gi_marshalling_tests_garray_utf8_full_inout:
 * @array_: (inout) (element-type utf8) (transfer full):
 */
void
gi_marshalling_tests_garray_utf8_full_inout (GArray **array_)

/**
 * gi_marshalling_tests_gptrarray_utf8_full_inout:
 * @parray_: (inout) (element-type utf8) (transfer full):
 */
void
gi_marshalling_tests_gptrarray_utf8_full_inout (GPtrArray **parray_)
Comment 2 GNOME Infrastructure Team 2018-02-08 12:33:01 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gobject-introspection/issues/124.