{"id":3175,"date":"2018-07-07T00:01:09","date_gmt":"2018-07-07T07:01:09","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=3175"},"modified":"2018-06-30T10:37:44","modified_gmt":"2018-06-30T17:37:44","slug":"made-up-file-names","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=3175","title":{"rendered":"Made-Up File Names"},"content":{"rendered":"

Many moons ago, I coded a file-renaming utility. It allows me to shuffle chapter names for documents used in my books, renaming a whole batch at once without overwriting existing filenames. It couldn’t happen if I didn’t know about the mktemp()<\/em> function.
\n
\nDefined in the unistd.h<\/code> header file, the mktemp(<\/em>) function generates a temporary filename. Technically, it generates a string, one that’s unique but based on a pattern or template you provide. Here’s how I use it in my file-renaming utility:<\/p>\n

t = mktemp(\"gbXXXXXX\");<\/code><\/p>\n

The immediate string constant \"gbXXXXXX\"<\/code> provides the filename template. The X’s in the string are replaced by random characters. The resulting string is saved in char<\/em> pointer variable t<\/code>. The code moves on to use that temporary filename.<\/p>\n

Here’s a sample program:<\/p>\n

\r\n#include <stdio.h>\r\n#include <unistd.h>\r\n\r\nint main()\r\n{\r\n    char template[] = \"tempXXXX\";\r\n    char *tempname;\r\n\r\n    tempname = mktemp(template);\r\n    printf(\"Temporary filename is '%s' or '%s'\\n\",\r\n            tempname,template);\r\n\r\n    return(0);\r\n}<\/pre>\n
Sample run:<\/p>\n
Temporary filename is 'tempmCcZ' or 'tempmCcZ'<\/code><\/pre>\n
When you run it again, you get different output:<\/p>\n
Temporary filename is 'tempzGUA' or 'tempzGUA'<\/code><\/pre>\n
In the code, the mktemp()<\/em> function takes the template, tempXXXX<\/code> and replaces the uppercase X characters with other, random characters. The result is returned as referenced in the tempname<\/code> pointer, but the buffer itself is also changed, as shown in the output.<\/p>\n
Because the mktemp()<\/em> function overwrites the template, it creates an interesting problem when you must generate more than one temporary filename based on the same pattern. To resolve this issue, you retain the template by copying it into a temporary buffer, such as temp[]<\/code> used in this example:<\/p>\n
\r\n#include <stdio.h>\r\n#include <unistd.h>\r\n#include <string.h>\r\n\r\nint main(void)\r\n{\r\n    char temp[9];\r\n    char template[] = \"tempXXXX\";\r\n    char *t;\r\n    int x;\r\n\r\n    for(x=0;x<10;x++)\r\n    {\r\n        strcpy(temp,template);\r\n        t = mktemp(temp);\r\n        puts(t);\r\n    }\r\n\r\n    return(0);\r\n}<\/pre>\n
The strcpy()<\/em> function at Line 14 copies the template<\/code> into the temp<\/code> buffer. Then mktemp()<\/em> at Line 15 uses that buffer to generate the temporary filename. Here’s the output:<\/p>\n
tempAnWr\r\ntempdVoi\r\ntempGPwb\r\ntempvFm8\r\ntemp8Pkl\r\ntemp2scJ\r\ntemp9cFf\r\ntempoOcn\r\ntempyher\r\ntemphAwd<\/code><\/pre>\n
These filenames are available for use in your code, guaranteed by the function not to exist. Variations on the mktemp()<\/em> function take the action further and actually create the temporary file — or even a directory. You can read more details in the man<\/em> pages.<\/p>\n
One more point! The mktemp()<\/em> function returns the NULL<\/code> pointer when it’s unable to do its job. For the code you plan on running in the wild, ensure that you check for NULL<\/code> after the mktemp()<\/em> function returns its value.<\/p>\n","protected":false},"excerpt":{"rendered":"
Are you tired of using foo<\/code> and temp<\/code> as temporary filenames? The C library has a solution for you. 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-3175","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\/3175","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=3175"}],"version-history":[{"count":5,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3175\/revisions"}],"predecessor-version":[{"id":3186,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/3175\/revisions\/3186"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3175"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3175"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}