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 574660 - API: need g_module_open() variant with GError
API: need g_module_open() variant with GError
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gmodule
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on: 671212
Blocks:
 
 
Reported: 2009-03-09 17:13 UTC by Tim-Philipp Müller
Modified: 2018-05-24 11:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tim-Philipp Müller 2009-03-09 17:13:43 UTC 
I was surprised to find that the GModule API doesn't use GError.

I think there should be some kind of g_module_open_full() function which returns a GError in case of failure.

This is useful to distinguish between the case where opening the module failed because of some error, or the file just didn't exist in the first place, for example.

This would also make things consistent with the rest of the GLib-2.x API.
Comment 1 GNOME Infrastructure Team 2018-05-24 11:47:37 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/glib/issues/203.