2012-07-06 19:50:00 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
2015-06-18 20:47:44 +03:00
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2020-11-09 07:23:58 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1 - or - later -->
2012-07-06 19:50:00 +04:00
2018-06-06 12:59:04 +03:00
<refentry id= "sd_id128_to_string" xmlns:xi= "http://www.w3.org/2001/XInclude" >
2012-07-06 19:50:00 +04:00
2015-02-04 05:14:13 +03:00
<refentryinfo >
<title > sd_id128_to_string</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > sd_id128_to_string</refentrytitle>
<manvolnum > 3</manvolnum>
</refmeta>
<refnamediv >
<refname > sd_id128_to_string</refname>
2021-08-20 11:51:53 +03:00
<refname > SD_ID128_TO_STRING</refname>
2015-02-04 05:14:13 +03:00
<refname > sd_id128_from_string</refname>
2021-08-20 11:51:53 +03:00
<refname > SD_ID128_STRING_MAX</refname>
2015-02-04 05:14:13 +03:00
<refpurpose > Format or parse 128-bit IDs as strings</refpurpose>
</refnamediv>
<refsynopsisdiv >
<funcsynopsis >
<funcsynopsisinfo > #include < systemd/sd-id128.h> </funcsynopsisinfo>
2021-08-20 11:51:53 +03:00
<funcsynopsisinfo > #define SD_ID128_STRING_MAX 33U</funcsynopsisinfo>
<funcsynopsisinfo > #define SD_ID128_TO_STRING(id) …</funcsynopsisinfo>
2015-02-04 05:14:13 +03:00
<funcprototype >
<funcdef > char *<function > sd_id128_to_string</function> </funcdef>
2021-08-20 11:51:53 +03:00
<paramdef > sd_id128_t <parameter > id</parameter> , char <parameter > s</parameter> [static SD_ID128_STRING_MAX]</paramdef>
2015-02-04 05:14:13 +03:00
</funcprototype>
<funcprototype >
<funcdef > int <function > sd_id128_from_string</function> </funcdef>
<paramdef > const char *<parameter > s</parameter> , sd_id128_t *<parameter > ret</parameter> </paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
2021-08-20 11:51:53 +03:00
<para > <function > sd_id128_to_string()</function> formats a 128-bit ID as a character string. It expects
the ID and a string array capable of storing 33 characters
(<constant > SD_ID128_STRING_MAX</constant> ). The ID will be formatted as 32 lowercase hexadecimal digits
and be terminated by a <constant > NUL</constant> byte.</para>
<para > <function > SD_ID128_TO_STRING()</function> is a macro that wraps
<function > sd_id128_to_string()</function> and passes an appropriately sized buffer as second argument,
allocated as C99 compound literal. Each use will thus implicitly acquire a suitable buffer on the stack
which remains valid until the end of the current code block. This is usually the simplest way to acquire
a string representation of a 128-bit ID in a buffer that is valid in the current code block.</para>
2015-02-04 05:14:13 +03:00
2021-08-20 11:51:53 +03:00
<para > <function > sd_id128_from_string()</function> implements the reverse operation: it takes a 33
character string with 32 hexadecimal digits (either lowercase or uppercase, terminated by
<constant > NUL</constant> ) and parses them back into a 128-bit ID returned in
<parameter > ret</parameter> . Alternatively, this call can also parse a 37-character string with a 128-bit
ID formatted as RFC UUID. If <parameter > ret</parameter> is passed as <constant > NULL</constant> the
function will validate the passed ID string, but not actually return it in parsed form.</para>
2015-02-04 05:14:13 +03:00
2021-06-15 18:55:17 +03:00
<para > Note that when parsing 37 character UUIDs this is done strictly in Big Endian byte order,
2021-08-20 11:51:53 +03:00
i.e. according to <ulink url= "https://tools.ietf.org/html/rfc4122" > RFC4122</ulink> Variant 1 rules, even
if the UUID encodes a different variant. This matches behaviour in various other Linux userspace
tools. It's probably wise to avoid UUIDs of other variant types.</para>
<para > For more information about the <literal > sd_id128_t</literal> type see
<citerefentry > <refentrytitle > sd-id128</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> . Note that
these calls operate the same way on all architectures, i.e. the results do not depend on
endianness.</para>
<para > When formatting a 128-bit ID into a string, it is often easier to use a format string for
<citerefentry
project='man-pages'><refentrytitle > printf</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> . This
is easily done using the <constant > SD_ID128_FORMAT_STR</constant> and
<function > SD_ID128_FORMAT_VAL()</function> macros. For more information see
2015-02-04 05:14:13 +03:00
<citerefentry > <refentrytitle > sd-id128</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> .</para>
</refsect1>
<refsect1 >
<title > Return Value</title>
2021-08-20 11:51:53 +03:00
<para > <function > sd_id128_to_string()</function> always succeeds and returns a pointer to the string array
passed in. <function > sd_id128_from_string()</function> returns 0 on success, in which case
<parameter > ret</parameter> is filled in, or a negative errno-style error code.</para>
2015-02-04 05:14:13 +03:00
</refsect1>
2018-06-06 12:59:04 +03:00
<xi:include href= "libsystemd-pkgconfig.xml" />
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > sd-id128</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> ,
<citerefentry project= 'man-pages' > <refentrytitle > printf</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry>
</para>
</refsect1>
2012-07-06 19:50:00 +04:00
</refentry>