mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-07-21 01:17:51 +02:00
GDBus: Add G_DBUS_METHOD_INVOCATION_HANDLED, _UNHANDLED
Like G_SOURCE_REMOVE and G_SOURCE_CONTINUE, these make it clearer what it means to return TRUE or FALSE. In particular, in GDBus methods that fail, the failure case still needs to return TRUE (unlike the typical GError pattern), leading to comments like this: g_dbus_method_invocation_return_error (invocation, ...); return TRUE; /* handled */ which can now be replaced by: g_dbus_method_invocation_return_error (invocation, ...); return G_DUS_METHOD_INVOCATION_HANDLED; G_DBUS_METHOD_INVOCATION_UNHANDLED is added for symmetry, but is very rarely (perhaps never?) useful in practice. Signed-off-by: Simon McVittie <smcv@collabora.com>
This commit is contained in:
committed by
Philip Withnall
parent
500d065f3d
commit
d65c8c30a9
@@ -1522,7 +1522,7 @@ class CodeGenerator:
|
||||
' *\n'
|
||||
' * If a signal handler returns %%TRUE, it means the signal handler will handle the invocation (e.g. take a reference to @invocation and eventually call %s_complete_%s() or e.g. g_dbus_method_invocation_return_error() on it) and no order signal handlers will run. If no signal handler handles the invocation, the %%G_DBUS_ERROR_UNKNOWN_METHOD error is returned.\n'
|
||||
' *\n'
|
||||
' * Returns: %%TRUE if the invocation was handled, %%FALSE to let other signal handlers run.\n'
|
||||
' * Returns: %%G_DBUS_METHOD_INVOCATION_HANDLED or %%TRUE if the invocation was handled, %%G_DBUS_METHOD_INVOCATION_UNHANDLED or %%FALSE to let other signal handlers run.\n'
|
||||
%(i.name, m.name, i.name_lower, m.name_lower), False))
|
||||
self.write_gtkdoc_deprecated_and_since_and_close(m, self.outfile, 2)
|
||||
if m.unix_fd:
|
||||
|
Reference in New Issue
Block a user