Provided by: libelogind-dev-doc_241.3-1+debian1_all bug

NAME

       sd_bus_message_verify_type - Check if the message has specified type at the current
       location

SYNOPSIS

       #include <elogind/sd-bus.h>

       int sd_bus_message_verify_type(sd_bus_message *m, char type, const char* contents);

DESCRIPTION

       sd_bus_message_verify_type() checks if the complete type at the current location in the
       message m matches the specified type and contents. If non-zero, parameter type must be one
       of the types specified in sd_bus_message_append(1). If non-null, parameter contents must
       be a valid sequence of complete types. If both type and contents are specified type must
       be a container type.

       If type is specified, the type in the message must match. If contents is specified, the
       type in the message must be a container type with this signature.

RETURN VALUE

       On success, this call returns true if the type matches and zero if not (the message m
       contains different data or the end of the message has been reached). On failure, it
       returns a negative errno-style error code.

ERRORS

       Returned errors may indicate the following problems:

       -EINVAL
           m or both type and contents are NULL.

           Arguments do not satisfy other contraints listed above.

       -EPERM
           Message m is not sealed.

NOTES

       These APIs are implemented as a shared library, which can be compiled and linked to with
       the libelogind pkg-config(1) file.

SEE ALSO

       elogind(1), sd-bus(3), sd_bus_message_append(3)