2014-11-21 22:44:48 +03:00
<?xml version='1.0'?> <!-- * - Mode: nxml; nxml - child - indent: 2; indent - tabs - mode: nil - * -->
2014-03-07 08:24:20 +04:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2015-05-27 12:38:19 +03:00
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % entities SYSTEM "custom-entities.ent" >
%entities;
]>
2014-03-07 08:24:20 +04:00
<!--
2015-03-14 05:26:47 +03:00
This file is part of systemd.
2014-03-07 08:24:20 +04:00
2015-03-14 05:26:47 +03:00
Copyright 2014 Zbigniew Jędrzejewski-Szmek
2014-03-07 08:24:20 +04:00
2015-03-14 05:26:47 +03:00
systemd is free software; you can redistribute it and/or modify it
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
(at your option) any later version.
2014-03-07 08:24:20 +04:00
2015-03-14 05:26:47 +03:00
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
2014-03-07 08:24:20 +04:00
2015-03-14 05:26:47 +03:00
You should have received a copy of the GNU Lesser General Public License
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
2014-03-07 08:24:20 +04:00
-->
2015-06-17 13:32:33 +03:00
<refentry id= "sd_bus_message_append_array"
2014-03-07 08:24:20 +04:00
xmlns:xi="http://www.w3.org/2001/XInclude">
<refentryinfo >
<title > sd_bus_message_append_array</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > A monkey with a typewriter</contrib>
<firstname > Zbigniew</firstname>
<surname > Jędrzejewski-Szmek</surname>
<email > zbyszek@in.waw.pl</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > sd_bus_message_append_array</refentrytitle>
<manvolnum > 3</manvolnum>
</refmeta>
<refnamediv >
<refname > sd_bus_message_append_array</refname>
<refname > sd_bus_message_append_array_memfd</refname>
<refname > sd_bus_message_append_array_iovec</refname>
<refname > sd_bus_message_append_array_space</refname>
<refpurpose > Attach an array of items to a message</refpurpose>
</refnamediv>
<refsynopsisdiv >
<funcsynopsis >
<funcsynopsisinfo > #include < systemd/sd-bus.h> </funcsynopsisinfo>
<funcprototype >
<funcdef > int sd_bus_message_append_array</funcdef>
<paramdef > sd_bus_message *<parameter > m</parameter> </paramdef>
<paramdef > char <parameter > type</parameter> </paramdef>
<paramdef > char void *<parameter > ptr</parameter> </paramdef>
<paramdef > size_t <parameter > size</parameter> </paramdef>
</funcprototype>
<funcprototype >
<funcdef > int sd_bus_message_append_array_memfd</funcdef>
<paramdef > sd_bus_message *<parameter > m</parameter> </paramdef>
<paramdef > char <parameter > type</parameter> </paramdef>
2014-08-18 15:28:43 +04:00
<paramdef > int <parameter > memfd</parameter> </paramdef>
2014-03-07 08:24:20 +04:00
</funcprototype>
<funcprototype >
<funcdef > int sd_bus_message_append_array_iovec</funcdef>
<paramdef > sd_bus_message *<parameter > m</parameter> </paramdef>
<paramdef > char <parameter > type</parameter> </paramdef>
<paramdef > const struct iovec *<parameter > iov</parameter> </paramdef>
<paramdef > unsigned <parameter > n</parameter> </paramdef>
</funcprototype>
<funcprototype >
<funcdef > int sd_bus_message_append_array_space</funcdef>
<paramdef > char <parameter > type</parameter> </paramdef>
<paramdef > size_t <parameter > size</parameter> </paramdef>
<paramdef > char void **<parameter > ptr</parameter> </paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2014-05-08 03:28:45 +04:00
<para > The <function > sd_bus_message_append_array</function> functionc
2014-03-07 08:24:20 +04:00
appends items to message <parameter > m</parameter> as the single
array. A container will be opened, items appended, and the
container closed. Parameter <parameter > type</parameter> determines
how pointer <parameter > p</parameter> is interpreted.
<parameter > type</parameter> must be one of the "trivial" types
<literal > y</literal> , <literal > n</literal> , <literal > q</literal> ,
<literal > i</literal> , <literal > u</literal> , <literal > x</literal> ,
<literal > t</literal> , <literal > d</literal> (but not
<literal > b</literal> ), as defined by the
<ulink url= "http://dbus.freedesktop.org/doc/dbus-specification.html#basic-types" > Basic Types</ulink>
section of the D-Bus specification, and listed in
<citerefentry > <refentrytitle > sd_bus_message_append_basic</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> .
2014-07-23 14:40:07 +04:00
Pointer <parameter > p</parameter> must point to an array of size
2014-03-07 08:24:20 +04:00
<parameter > size</parameter> bytes containing items of the
respective type. Size <parameter > size</parameter> must be a
multiple of the size of the type <parameter > type</parameter> . As a
special case, <parameter > p</parameter> may be
<constant > NULL</constant> , if <parameter > size</parameter> is 0.
</para>
<para > The memory pointed at by <parameter > p</parameter> is copied
into the memory area containing the message and may be changed
after this call.</para>
2014-05-08 03:28:45 +04:00
<para > The
<function > sd_bus_message_append_array_memfd</function> function appends
2014-03-07 08:24:20 +04:00
items to message <parameter > m</parameter> , similarly to
<function > sd_bus_message_append_array</function> . Contents of the
memory file descriptor <parameter > memfd</parameter> are used as
the contents of the array. Their size must be a multiple of the
size of the type <parameter > type</parameter> .</para>
2014-05-08 03:28:45 +04:00
<para > The descriptor specified with <parameter > memfd</parameter>
will be sealed and cannot be modified after this call.</para>
2014-03-07 08:24:20 +04:00
2014-05-08 03:28:45 +04:00
<para > The
<function > sd_bus_message_append_array_iovec</function> function appends
2014-03-07 08:24:20 +04:00
items to message <parameter > m</parameter> , similarly to
<function > sd_bus_message_append_array</function> . Contents of the
iovec <parameter > iov</parameter> are used as the contents of the
array. The total size of <parameter > iov</parameter> payload (the
sum of <structfield > iov_len</structfield> fields) must be a multiple
of the size of the type <parameter > type</parameter> .</para>
2014-05-08 03:28:45 +04:00
<para > The <parameter > iov</parameter> argument must point to
2014-03-07 08:24:20 +04:00
<parameter > n</parameter> <structname > struct iovec</structname>
structures. Each structure may have the
<structname > iov_base</structname> field set, in which case the
memory pointed to will be copied into the message, or unset, in
which case a block of zeros of length
<structname > iov_len</structname> bytes will be inserted. The
memory pointed at by <parameter > iov</parameter> may be changed
after this call.</para>
2014-05-08 03:28:45 +04:00
<para > The
<function > sd_bus_message_append_array_space</function> function appends
2014-03-07 08:24:20 +04:00
space for an array of items to message <parameter > m</parameter> .
It behaves the same as
<function > sd_bus_message_append_array</function> , but instead
of copying items to the message, it returns a pointer to the
destination area to the caller in pointer <parameter > p</parameter> .
</para>
</refsect1>
<refsect1 >
<title > Return Value</title>
2014-05-08 03:28:45 +04:00
<para > On success, these calls return 0 or a positive integer. On
2014-03-07 08:24:20 +04:00
failure, they returns a negative errno-style error code.</para>
</refsect1>
<xi:include href= "sd_bus_message_append_basic.xml" xpointer= "errors" />
<refsect1 >
<title > Notes</title>
<para > <function > sd_bus_append_array()</function> and other
functions described here are available as a shared library, which
can be compiled and linked to with the
man: add a mapping for external manpages
It is annoying when we have dead links on fd.o.
Add project='man-pages|die-net|archlinux' to <citerefentry>-ies.
In generated html, add external links to
http://man7.org/linux/man-pages/man, http://linux.die.net/man/,
https://www.archlinux.org/.
By default, pages in sections 2 and 4 go to man7, since Michael
Kerrisk is the autorative source on kernel related stuff.
The rest of links goes to linux.die.net, because they have the
manpages.
Except for the pacman stuff, since it seems to be only available from
archlinux.org.
Poor gummiboot gets no link, because gummitboot(8) ain't to be found
on the net. According to common wisdom, that would mean that it does
not exist. But I have seen Kay using it, so I know it does, and
deserves to be found. Can somebody be nice and put it up somewhere?
2014-07-08 02:25:54 +04:00
<constant > libsystemd</constant> <citerefentry project= 'die-net' > <refentrytitle > pkg-config</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
2014-03-07 08:24:20 +04:00
file.</para>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > sd-bus</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > sd_bus_message_append</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > sd_bus_message_append_basic</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
<ulink url= "http://dbus.freedesktop.org/doc/dbus-specification.html" > The D-Bus specification</ulink>
</para>
</refsect1>
</refentry>