From 979bdc47c9cda3960009525d4a870419f04bfc5d Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Tue, 28 Jan 2020 16:28:04 +0100 Subject: man: enclose C type names in --- man/sd_bus_message_read.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'man/sd_bus_message_read.xml') diff --git a/man/sd_bus_message_read.xml b/man/sd_bus_message_read.xml index 526fb0e70a..aa3cffb432 100644 --- a/man/sd_bus_message_read.xml +++ b/man/sd_bus_message_read.xml @@ -60,13 +60,13 @@ For each type specified in the type string, one or more arguments need to be specified after the types parameter, in the same order. The arguments must be - pointers to appropriate types (a pointer to int8_t for a y in - the type string, a pointer to int32_t for an i, a pointer to - const char* for an s, ...) which are set based on the values in + pointers to appropriate types (a pointer to int8_t for a y in + the type string, a pointer to int32_t for an i, a pointer to + const char* for an s, ...) which are set based on the values in the message. As an exception, in case or array and variant types, the first argument is an "input" argument that further specifies how the message should be read. See the table below for a complete list of allowed arguments and their types. Note that, if the basic type is a pointer - (e.g., const char * in the case of a string), the argument is a pointer to a + (e.g., const char * in the case of a string), the argument is a pointer to a pointer, and also the pointer value that is written is only borrowed and the contents must be copied if they are to be used after the end of the messages lifetime. @@ -99,7 +99,7 @@ a SD_BUS_TYPE_ARRAY array - int, which specifies the expected length n of the array + int, which specifies the expected length n of the array n sets of arguments appropriate for the array element type -- cgit v1.2.3