luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2024-12-25 15:06:14 +01:00
Code Issues Packages Projects Releases Wiki Activity

gsignal: update documentation about va_marshaller

Browse Source 
If we specify a c_marshaller, g_signal_newv() will never assign an
va_marshaller automatically. So either use NULL (for simple cases), or
specify both to avoid the generic performance penalty.
This commit is contained in:
Christian Hergert 2019-05-30 18:41:02 -07:00
parent 833d38b40f
commit 266a292a35
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
gobject/gsignal.c
View File

@ -1410,8 +1410,14 @@ g_signal_query (guint signal_id,
* in their class_init method by doing super_class->signal_handler = my_signal_handler.
* Instead they will have to use g_signal_override_class_handler().
*
* If c_marshaller is %NULL, g_cclosure_marshal_generic() will be used as
* the marshaller for this signal.
* If @c_marshaller is %NULL, g_cclosure_marshal_generic() will be used as
* the marshaller for this signal. In some simple cases, g_signal_new()
* will use a more optimized c_marshaller and va_marshaller for the signal
* instead of g_cclosure_marshal_generic().
*
* If @c_marshaller is non-%NULL, you need to also specify a va_marshaller
* using g_signal_set_va_marshaller() or the generic va_marshaller will
* be used.
*
* Returns: the signal id
*/