{"id":3934,"date":"2020-01-11T00:01:23","date_gmt":"2020-01-11T08:01:23","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=3934"},"modified":"2020-01-04T09:33:53","modified_gmt":"2020-01-04T17:33:53","slug":"fun-with-the-asprintf-function","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=3934","title":{"rendered":"Fun with the asprintf()<\/em> Function"},"content":{"rendered":"

If you desire to store formatted output in a buffer, the snprintf()<\/em> function, covered in last week’s Lesson<\/a>, is a safe alternative to the standard Library sprintf()<\/em> function. An even better choice is the asprintf()<\/em> function.
\n
\nThe asprintf()<\/em> function sends formatted output into a perfectly-sized buffer, allocated within the function itself. Here is its man<\/em> page format:<\/p>\n

int asprintf(char **ret, const char *format, ...);<\/code><\/p>\n

The first argument is the scary pointer-pointer thing, but it’s really the address of a pointer. When the function returns, the pointer contains the formatted output string; the final two arguments are the same as for the standard printf()<\/em> function: a format string and variable argument list.<\/p>\n

Sample code:<\/p>\n

\r\n#include <stdio.h>\r\n\r\nint main()\r\n{\r\n    char *buffer;\r\n    int r;\r\n\r\n    r = asprintf(&buffer,\"The total is %d\\n\",5+8);\r\n\r\n    puts(buffer);\r\n    printf(\"%d characters generated\\n\",r);\r\n\r\n    return(0);\r\n}<\/pre>\n
The char<\/em> pointer buffer<\/code> is declared at Line 5. Its address is passed to the asprintf()<\/em> function at Line 8.<\/p>\n
Within the asprintf()<\/em> function, the buffer is allocated, the size properly set to be filled with the formatted output. No overflow is possible.<\/p>\n
The buffer’s contents are output at Line 11. The asprintf()<\/em> function’s return value, stored in variable r<\/code>, is also output. This value is equal to the length of the string returned (the size of the buffer, minus one for the null character):<\/p>\n
The total is 13<\/p>\n
16 characters generated<\/code><\/p>\n
Using this function is far safer than using the sprintf()<\/em> function, which doesn’t check for buffer overflow. And it’s better than the snprintf()<\/em> function, which has a set buffer size. With the asprintf()<\/em> function, the buffer size can be anything; all you must do is supply a char<\/em> pointer to reference the string created. Well, and get over any double-pointer fears you harbor. Speaking of which, here is the double-pointer version of the same code:<\/p>\n
\r\n#include <stdio.h>\r\n\r\nint main()\r\n{\r\n    char **buffer;\r\n    int r;\r\n\r\n    r = asprintf(buffer,\"The total is %d\\n\",5+8);\r\n\r\n    puts(*buffer);\r\n    printf(\"%d characters generated\\n\",r);\r\n\r\n    return(0);\r\n}<\/pre>\n
The double-pointer buffer<\/code> is declared at Line 5. It’s passed directly as the first argument of asprintf()<\/em> at Line 8; no need to prefix it with an ampersand.<\/p>\n
Line 10 uses the *buffer<\/code> argument in the puts()<\/em> function. The format *buffer<\/code> refers to the string, whereas **buffer<\/code> refers to the string’s address. Yes, it’s all complicated pointer nonsense, yet the code runs identically to the first example.<\/p>\n
If you the -Wall<\/code> switch to build this second example of the code, you may see an uninitialized pointer warning. Ignore it. The warning is legitimate but the fix, which is to initialize the pointer to NULL<\/em>, may crash the program. It’s safe to pass the uninitialized **buffer<\/code> pointer to the asprintf()<\/em> function because the function itself initializes it.<\/p>\n
The **buffer<\/code> or &buffer<\/code> format is required because a pointer must be passed indirectly to a function that modifies the pointer’s address. Otherwise the function loses the pointer’s address when it returns, which defeats the purpose. You can read my series of Lessons<\/a> on this topic if it confuses you or you need to brush-up.<\/p>\n","protected":false},"excerpt":{"rendered":"
A smart function, asprintf()<\/em> both allocates and sizes a buffer into which formatted output is stored. Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-3934","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3934","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3934"}],"version-history":[{"count":3,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3934\/revisions"}],"predecessor-version":[{"id":3939,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3934\/revisions\/3939"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3934"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3934"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}