{"id":1227,"date":"2015-03-07T00:01:08","date_gmt":"2015-03-07T08:01:08","guid":{"rendered":"http:\/\/c-for-dummies.com\/blog\/?p=1227"},"modified":"2015-02-28T08:06:53","modified_gmt":"2015-02-28T16:06:53","slug":"other-ways-to-fetch-the-cwd","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=1227","title":{"rendered":"Other Ways to Fetch the CWD"},"content":{"rendered":"

In last week’s Lesson<\/a> I mentioned the constant, MAXPATHLEN<\/code>. Like PATH_MAX<\/code>, it returns the size of the maximum number of characters allowed in a pathname. Unlike PATH_MAX<\/code>, however, MAXPATHLEN<\/code> is defined in the sys\/param.h<\/code> header file, not limits.h<\/code>.
\n
\nWhy the two constants? Who knows!<\/p>\n

A better question is to determine whether or not they’re equal. After all, internally one may be assigned to the other. To confirm whether that’s the case, you can go spelunking in the header files, or just write some quick code to compare the values:<\/p>\n

\r\n#include <stdio.h>\r\n#include <limits.h>\r\n#include <sys\/param.h>\r\n\r\nint main()\r\n{\r\n\tprintf(\"The value of PATH_MAX is %d\\n\",PATH_MAX);\r\n\tprintf(\"The value of MAXPATHLEN is %d\\n\",MAXPATHLEN);\r\n\r\n\treturn(0);\r\n}<\/pre>\n
Here is the output on my Mac:<\/p>\n
The value of PATH_MAX is 1024\r\nThe value of MAXPATHLEN is 1024<\/code><\/pre>\n
By exploring the header files, I found the following line in sys.param.h<\/code>:<\/p>\n
#define MAXPATHLEN      PATH_MAX<\/code><\/pre>\n
There it is! So MAXPATHLEN<\/code> is directly related to PATH_MAX<\/code>, which is frequently the case when two constants represent the same value. One constant (probably MAXPATHLEN<\/code>) is historical and included for backwards compatibility.<\/p>\n
While exploring these two constants, I noticed another function for reading the current directory, getwd()<\/em>.<\/p>\n
Like getcwd()<\/em>, the getwd()<\/em> function also returns the current working directory. It requires the unistd.h<\/code> header file. It’s a bit more concise than the getcwd()<\/em> function, and it’s capable of returning a directory in one punch, as the following code demonstrates:<\/p>\n
\r\n#include <stdio.h>\r\n#include <unistd.h>\r\n\r\nint main()\r\n{\r\n\tprintf(\"Current directory is '%s'\\n\",getwd(NULL));\r\n\r\n\treturn(0);\r\n}<\/pre>\n
So why isn’t everyone using getwd()<\/em> instead of getcwd()<\/em>? How could I make such an oversight in my books? Easy.<\/p>\n
While using getwd()<\/em> is pretty nifty, as the one-statement code above demonstrates, it’s not the best function choice for a variety of reasons.<\/p>\n
I stumbled upon getwd()<\/em> as I was exploring the C library man pages. I recommend that you do so as well: Look up an item in the man pages and see the related functions. It’s a great way to expand your C knowledge.<\/p>\n
On the man page for getwd()<\/em> (shared with getcwd()<\/em>), it states the following:<\/p>\n
\r\nBUGS<\/strong>\r\n     The getwd<\/strong>() function does not do sufficient error checking and is not\r\n     able to return very long, but valid, paths.  It is provided for compati-\r\n     bility.<\/code><\/pre>\n
The getwd()<\/em> function apparently had some serious issues, so it was deprecated a while back. The current version is provided for compatibility and it calls getcwd()<\/em> internally. So if you’re going to learn and use a C library function to fetch the current directory, use getcwd()<\/em>, which is the function covered in my books.<\/p>\n","protected":false},"excerpt":{"rendered":"
The faster, more compact current working directory function. Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-1227","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\/1227","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=1227"}],"version-history":[{"count":6,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1227\/revisions"}],"predecessor-version":[{"id":1256,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1227\/revisions\/1256"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1227"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1227"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1227"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}