luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-12-10 10:33:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

Eradicate links and xrefs

Browse Source 
These are all replaced by markdown ref links.
This commit is contained in:
Matthias Clasen
2014-02-08 12:26:56 -05:00
parent 1448e619b5
commit e7fd3de86d
70 changed files with 460 additions and 521 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
gobject/gclosure.c
View File

@@ -61,9 +61,8 @@
* marshaller for any closure which is connected to this
* signal. GObject provides a number of C marshallers for this
* purpose, see the g_cclosure_marshal_*() functions. Additional C
* marshallers can be generated with the <link
* linkend="glib-genmarshal">glib-genmarshal</link> utility. Closures
* can be explicitly connected to signals with
* marshallers can be generated with the [glib-genmarshal][glib-genmarshal]
* utility. Closures can be explicitly connected to signals with
* g_signal_connect_closure(), but it usually more convenient to let
* GObject create a closure automatically by using one of the
* g_signal_connect_*() functions which take a callback function/user
@@ -308,9 +307,8 @@ g_closure_set_meta_va_marshal (GClosure *closure,
* Sets the meta marshaller of @closure. A meta marshaller wraps
* @closure->marshal and modifies the way it is called in some
* fashion. The most common use of this facility is for C callbacks.
* The same marshallers (generated by <link
* linkend="glib-genmarshal">glib-genmarshal</link>) are used
* everywhere, but the way that we get the callback function
* The same marshallers (generated by [glib-genmarshal][glib-genmarshal]),
* are used everywhere, but the way that we get the callback function
* differs. In most cases we want to use @closure->callback, but in
* other cases we want to use some different technique to retrieve the
* callback function.