Provided by: libsystemd-dev_251.4-1ubuntu7_amd64 bug


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


       #include <systemd/sd-bus.h>

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


       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.


       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.

       Returned errors may indicate the following problems:

           m or both type and contents are NULL.

           Arguments do not satisfy other constraints listed above.

           Message m is not sealed.


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


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