sd_bus_message_append_basic — Attach a single field to a message
|const void *p|
sd_bus_message_append_basic() appends a
single field to the message
type determines how the pointer
p is interpreted.
type must be one of the basic types as
defined by the Basic
Types section of the D-Bus specification, and listed in
the table below.
Table 1. Item type specifiers
|Specifier||Constant||Description||Size||Expected C Type|
|"||unsigned integer||1 byte||uint8_t|
|"||signed integer||2 bytes||int16_t|
|"||unsigned integer||2 bytes||uint16_t|
|"||signed integer||4 bytes||int32_t|
|"||unsigned integer||4 bytes||uint32_t|
|"||signed integer||8 bytes||int64_t|
|"||unsigned integer||8 bytes||uint64_t|
|"||UNIX file descriptor||4 bytes||int|
The value of the parameter is copied into a memory area held
by the message object, stays in the possession of the caller and
may hence be freely changed after this call without affecting the
bus message it has been added to. If
h" (UNIX file descriptor), the descriptor is
duplicated by this call and the passed descriptor stays in
possession of the caller.
For types "
g", the parameter
interpreted as a pointer to a
character sequence. As a special case, a
pointer is interpreted as an empty string. The string should be
valid Unicode string encoded as UTF-8. In case of the two latter
types, the additional requirements for a D-Bus object path or
type signature should be satisfied. Those requirements should be
verified by the recipient of the message.
On success, this call returns 0 or a positive integer. On failure, it returns a negative errno-style error code.
Functions described here are available as a shared
library, which can be compiled against and linked to with the
The code described here uses
which is declared to be not multi-thread-safe. This means that the code calling the functions described
here must not call
from a parallel thread. It is recommended to only do calls to
from an early phase of the program when no other threads have been started.