sd_bus_message_read(3)

.SH "NAME" sd_bus_message_read, sd_bus_message_readv, sd_bus_message_peek_type - Read a sequence of values from a message

.SH "SYNOPSIS"

#include <systemd/sd-bus.h>

.HP 576u int sd_bus_message_read(sd_bus_message *m, const char *types, ...);

.HP 600u int sd_bus_message_readv(sd_bus_message *m, const char *types, va_list ap);

.HP 696u int sd_bus_message_peek_type(sd_bus_message *m, char *type, const char **contents);

.SH "DESCRIPTION"

.PP sd_bus_message_read() reads a sequence of fields from the D-Bus message object m and advances the read position in the message. The type string types describes the types of items expected in the message and the field arguments that follow. The type string may be NULL or empty, in which case nothing is read.

.PP The type string is composed of the elements described in sd_bus_message_append(3), i.e. basic and container types. It must contain zero or more single "complete types". The type string is NUL-terminated.

.PP 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 the message. As an exception, in case of 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 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 message's lifetime. If the type is h (UNIX file descriptor), the descriptor is not duplicated by this call and the returned descriptor remains in possession of the message object, and needs to be duplicated by the caller in order to keep an open reference to it after the message object is freed.

.PP Each argument may also be NULL, in which case the value is read and ignored.

.sp
Table 1. Item type specifiers

.PP If objects of the specified types are not present at the current position in the message, an error is returned.

.PP The sd_bus_message_readv() is equivalent to the sd_bus_message_read(), except that it is called with a va_list instead of a variable number of arguments. This function does not call the va_end() macro. Because it invokes the va_arg() macro, the value of ap is undefined after the call.

.PP sd_bus_message_peek_type() determines the type of the next element in m to be read by sd_bus_message_read() or similar functions. On success, the type is stored in type, if it is not NULL. If the type is a container type, the type of its elements is stored in contents, if it is not NULL. If this function successfully determines the type of the next element in m, it returns a positive integer. If there are no more elements to be read, it returns zero.

.SH "RETURN VALUE"

.PP On success, these functions return a non-negative integer. On failure, they return a negative errno-style error code.

.SS "Errors"

.PP Returned errors may indicate the following problems:

.PP -EINVAL

sd_bus_message *m;
int64_t x;
sd_bus_message_read(m, "x", &x);

sd_bus_message *m;
int x; /* Do not use C99 "bool" type here, it is typically smaller


          in memory and would cause memory corruption */
sd_bus_message_read(m, "b", &x);

uint8_t y;
int16_t n;
uint16_t q;
int32_t i;
uint32_t u;
int64_t x;
uint64_t t;
double d;
sd_bus_message_read(m, "ynqiuxtd", &y, &n, &q, &i, &u, &x, &t, &d);

const char *s, *p;
sd_bus_message_read(m, "(so)", &s, &p);

const char *s;
uint64_t *v;
sd_bus_message_read(m, "v", "gt", &s, &v);

int i, j, k;
const char *s, *t, *u;
sd_bus_message_read(m, "a{is}", 3, &i, &s, &j, &t, &k, &u);

sd_bus_message *m;
int fd, fd_copy;
sd_bus_message_read(m, "h", &fd);
fd_copy = fcntl(fd, FD_DUPFD_CLOEXEC, 3);