committed by
Daan De Meyer
parent
a667ddf132
commit
e2b40db616
@@ -52,17 +52,19 @@
|
||||
</para>
|
||||
|
||||
<para>
|
||||
If <parameter>p</parameter> is not <constant>NULL</constant>, it should contain
|
||||
a pointer to an appropriate object. For example, if <parameter>type</parameter>
|
||||
is <constant>'y'</constant>, the object passed in <parameter>p</parameter>
|
||||
should have type <type>uint8_t *</type>. If <parameter>type</parameter> is
|
||||
<constant>'s'</constant>, the object passed in <parameter>p</parameter> should
|
||||
have type <type>const char **</type>. Note that, if the basic type is a pointer
|
||||
(e.g., <type>const char *</type> in the case of a string), the pointer is only
|
||||
borrowed and the contents must be copied if they are to be used after the end
|
||||
of the messages lifetime. Similarly, during the lifetime of such a pointer, the
|
||||
message must not be modified. See the table below for a complete list of allowed
|
||||
types.
|
||||
If <parameter>p</parameter> is not <constant>NULL</constant>, it should contain a pointer to an
|
||||
appropriate object. For example, if <parameter>type</parameter> is <constant>'y'</constant>, the object
|
||||
passed in <parameter>p</parameter> should have type <type>uint8_t *</type>. If
|
||||
<parameter>type</parameter> is <constant>'s'</constant>, the object passed in <parameter>p</parameter>
|
||||
should have type <type>const char **</type>. Note that, if the basic type is a pointer (e.g.,
|
||||
<type>const char *</type> in the case of a string), the pointer is only borrowed and the contents must
|
||||
be copied if they are to be used after the end of the messages lifetime. Similarly, during the lifetime
|
||||
of such a pointer, the message must not be modified. If <parameter>type</parameter> is
|
||||
<constant>'h'</constant> (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 (for example by calling
|
||||
<literal>fcntl(fd, FD_DUPFD_CLOEXEC, 3)</literal>). See the table below for a complete list of
|
||||
allowed types.
|
||||
</para>
|
||||
|
||||
<table id='format-specifiers'>
|
||||
|
||||
Reference in New Issue
Block a user