1SD_BUS_MESSAGE_VERIFY_TYPE(s3d)_bus_message_verify_tySpDe_BUS_MESSAGE_VERIFY_TYPE(3)
2
3
4
6 sd_bus_message_verify_type - Check if the message has specified type at
7 the current location
8
10 #include <systemd/sd-bus.h>
11
12 int sd_bus_message_verify_type(sd_bus_message *m, char type,
13 const char* contents);
14
16 sd_bus_message_verify_type() checks if the complete type at the current
17 location in the message m matches the specified type and contents. If
18 non-zero, parameter type must be one of the types specified in
19 sd_bus_message_append(1). If non-null, parameter contents must be a
20 valid sequence of complete types. If both type and contents are
21 specified type must be a container type.
22
23 If type is specified, the type in the message must match. If contents
24 is specified, the type in the message must be a container type with
25 this signature.
26
28 On success, this call returns true if the type matches and zero if not
29 (the message m contains different data or the end of the message has
30 been reached). On failure, it returns a negative errno-style error
31 code.
32
33 Errors
34 Returned errors may indicate the following problems:
35
36 -EINVAL
37 m or both type and contents are NULL.
38
39 Arguments do not satisfy other constraints listed above.
40
41 -EPERM
42 Message m is not sealed.
43
45 These APIs are implemented as a shared library, which can be compiled
46 and linked to with the libsystemd pkg-config(1) file.
47
49 systemd(1), sd-bus(3), sd_bus_message_append(3)
50
51
52
53systemd 250 SD_BUS_MESSAGE_VERIFY_TYPE(3)