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 556422 - g_file_enumerator_next_file: unclear whether return value needs to be freed
g_file_enumerator_next_file: unclear whether return value needs to be freed
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: docs
unspecified
Other All
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2008-10-15 15:29 UTC by Armin Burgmeier
Modified: 2008-10-16 04:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Armin Burgmeier 2008-10-15 15:29:11 UTC 
The documentation on g_file_enumerator_next_file is not clear on whether the return value needs to be unrefed or not. It seems it should, so a clarifying sentence such as "Free with g_object_unref() when no longer needed" for the description of the return value would be helpful.

http://library.gnome.org/devel/gio/unstable/GFileEnumerator.html#g-file-enumerator-next-file
Comment 1 Matthias Clasen 2008-10-16 04:19:58 UTC 
2008-10-16  Matthias Clasen  <mclasen@redhat.com>

        Bug 556422 – g_file_enumerator_next_file: unclear whether return
        value needs to be freed

        * gfileenumerator.c (g_file_enumerate_next_file): Clarify
        the return value docs. Pointed out by Armin Burgmeier