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 646314 - Suboptimal GLib.Object.connect() bindings
Suboptimal GLib.Object.connect() bindings
Status: RESOLVED OBSOLETE
Product: vala
Classification: Core
Component: Bindings: GLib
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Vala maintainers
Vala maintainers
Depends on:
Blocks:
 
 
Reported: 2011-03-31 08:15 UTC by Sebastian Dröge (slomo)
Modified: 2018-05-22 13:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastian Dröge (slomo) 2011-03-31 08:15:05 UTC 
The GLib.Object.connect() bindings seem to be a bit suboptimal and don't really make much sense in vala I guess... You must provide user_data passed to the signal handler and then depending on the prefix of the signal spec (signal:: vs. object-signal::) the user_data must be a GObject


I guess it would make more sense if GLib.Object.connect() would map to g_signal_connect() in one way or another so you could do o.connect("signal", callback), which behaves the same way as o.signal.connect(callback) without type checking
Comment 1 Jürg Billeter 2011-04-02 13:57:03 UTC 
g_signal_connect wouldn't be much better as we can't just disable type checking for the callback parameter. Please also note that it is already bound as GLib.Signal.connect.
Comment 2 Sebastian Dröge (slomo) 2013-07-17 13:26:16 UTC 
Ok, so what to do about this bug? :)
Comment 3 GNOME Infrastructure Team 2018-05-22 13:59:15 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/186.