From 7f9f55e1b3354c9565f62a2bf331f9b25db9650d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Sat, 11 Aug 2018 10:16:17 +0200 Subject: [PATCH] man: add sd_bus_message_read_array(3) --- man/rules/meson.build | 1 + man/sd-bus.xml | 3 +- man/sd_bus_message_read_array.xml | 108 ++++++++++++++++++++++++++++++ 3 files changed, 111 insertions(+), 1 deletion(-) create mode 100644 man/sd_bus_message_read_array.xml diff --git a/man/rules/meson.build b/man/rules/meson.build index 96b56569e3..548499d749 100644 --- a/man/rules/meson.build +++ b/man/rules/meson.build @@ -242,6 +242,7 @@ manpages = [ ''], ['sd_bus_message_new_signal', '3', [], ''], ['sd_bus_message_read', '3', ['sd_bus_message_readv'], ''], + ['sd_bus_message_read_array', '3', [], ''], ['sd_bus_message_read_basic', '3', [], ''], ['sd_bus_message_rewind', '3', [], ''], ['sd_bus_message_set_destination', diff --git a/man/sd-bus.xml b/man/sd-bus.xml index 7c0b3c1e6e..fbbd491ccb 100644 --- a/man/sd-bus.xml +++ b/man/sd-bus.xml @@ -65,8 +65,9 @@ sd_bus_message_new_method_call3, sd_bus_message_new_method_error3, sd_bus_message_new_signal3, -sd_bus_message_read_basic3, sd_bus_message_read3, +sd_bus_message_read_array3, +sd_bus_message_read_basic3, sd_bus_message_rewind3, sd_bus_message_set_destination3, sd_bus_message_set_expect_reply3, diff --git a/man/sd_bus_message_read_array.xml b/man/sd_bus_message_read_array.xml new file mode 100644 index 0000000000..31481272bb --- /dev/null +++ b/man/sd_bus_message_read_array.xml @@ -0,0 +1,108 @@ + + + + + + + + sd_bus_message_read_array + systemd + + + + sd_bus_message_read_array + 3 + + + + sd_bus_message_read_array + + Access an array of elements in a message + + + + + #include <systemd/sd-bus.h> + + + int sd_bus_message_read_array + sd_bus_message *m + char type + const void **ptr + size_t *size + + + + + + Description + + sd_bus_message_read_array() gives access to an element array in + message m. The "read pointer" in the message must be right before an + array of type type. As a special case, type may be + NUL, in which case any type is acceptable. A pointer to the array data is + returned in the parameter ptr and the size of array data (in bytes) is + returned in the parameter size. If size is 0, a + valid non-null pointer will be returned, but it may not be dereferenced. The data is aligned as + appropriate for the data type. The data is part of the message — it may not be modified and is + valid only as long as the message is referenced. After this function returns, the "read pointer" + points at the next element after the array. + + + + Return Value + + + On success, sd_bus_message_read_array() returns 0 or + a positive integer. On failure, it returns a negative errno-style error + code. + + + + + Errors + + Returned errors may indicate the following problems: + + + + -EINVAL + + Specified type is invalid or the message parameter or one of the output + parameters are NULL. + + + + -EOPNOTSUPP + + The byte order in the message is different than native byte + order. + + + + -EPERM + + The message is not sealed. + + + + -EBADMSG + + The message cannot be parsed. + + + + + + + See Also + + + systemd1, + sd-bus3, + sd_bus_message_read3 + + + +