X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=man%2Fsd_id128_to_string.xml;h=593d0752d58c397725c20be5e8dd1802575be46e;hb=a432cb691ca3c1e18b012cb8e9f6e5654b3652a2;hp=ec8b263e0d5b5def1f922845fed9ad3c93056976;hpb=bb31a4ac1997c189a344caf554f34c6aabc71aa7;p=elogind.git diff --git a/man/sd_id128_to_string.xml b/man/sd_id128_to_string.xml index ec8b263e0..593d0752d 100644 --- a/man/sd_id128_to_string.xml +++ b/man/sd_id128_to_string.xml @@ -59,7 +59,7 @@ int sd_id128_from_string - const char s[33], sd_id128_t* ret + const char* s, sd_id128_t* ret @@ -77,14 +77,19 @@ sd_id128_from_string() implements the reverse operation: it takes a 33 - character array with 32 hexadecimal digits - (terminated by NUL) and parses them back into an - 128 bit ID returned in - ret. + character string with 32 hexadecimal digits + (either lowercase or uppercase, terminated by NUL) and parses them back into an 128 + bit ID returned in + ret. Alternatively, this call + can also parse a 37 character string with a 128bit ID + formatted as RFC UUID. For more information about the sd_id128_t type see - sd-id1283. + sd-id1283. Note + that these calls operate the same way on all + architectures, i.e. the results do not depend on + endianess. When formatting a 128 bit ID into a string it is often easier to use a format string for