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 649644 - GLog function bindings are missing return values
GLog function bindings are missing return values
Status: RESOLVED OBSOLETE
Product: vala
Classification: Core
Component: Bindings: GLib
0.12.x
Other All
: Normal minor
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2011-05-07 10:51 UTC by Sam Thursfield
Modified: 2018-05-22 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch (883 bytes, patch)
2011-05-07 10:51 UTC, Sam Thursfield
reviewed Details | Review

Description Sam Thursfield 2011-05-07 10:51:47 UTC
Created attachment 187417 [details] [review]
Patch

Hi!
In glib-2.0.vapi, Log.set_default_handler(), Log.set_fatal_mask() and Log.set_always_fatal() have return values that are missing in the vapi. They return the old value of the settings, which is very useful to temporarily change the log level, when trying to trap warnings in unit tests etc.

Patch attached.
Comment 1 Luca Bruno 2011-05-12 14:04:15 UTC
commit a92b2cf1eb119d259abe5ce63898450060c46928
Author: Sam Thursfield <ssssam@gmail.com>
Date:   Thu May 12 16:00:26 2011 +0200

    glib-2.0: Fix Log.set_fatal_mask and set_always_fatal bindings
    
    Partially fixes bug 649644.

set_default_handler is "unbindable" at the moment because Vala doesn't support methods returning no user_data.
Comment 2 GNOME Infrastructure Team 2018-05-22 14:02:26 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/vala/issues/199.