DIRNAME
dirname, basename - Parse pathname components
#include <string.h> char *dirname(char*path ); char *basename(char *path);
dirname and basename break a null-terminated pathname string into directory and filename components. In the usual case, dirname returns the string up to, but not including, the final '/', and basename returns the component following the final '/'. Trailing '/' characters are not counted as part of the pathname.
If path does not contain a slash, dirname returns the string basename returns a copy of path. If path is the string dirname and basename return the string path is a NULL pointer or points to an empty string, then both dirname and basename return the string
Concatenating the string returned by dirname, a basename yields a complete pathname.
Both dirname and basename may modify the contents of path, so if you need to preserve the pathname string, copies should be passed to these functions. Furthermore, dirname and basename may return pointers to statically allocated memory which may overwritten by subsequent calls.
The following list of examples (taken from SUSv2) shows the strings returned by dirname and basename for different paths:
|^path|^dirname|^basename |"/usr/lib"|"/usr"|"lib" |"/usr/"|"/"|"usr" |"usr"|"."|"usr" |"/"|"/"|"/" |"."|"."|"." |".."|"."|".."
char *dirc, *basec, *bname, *dname; char *path = "/etc/passwd";
dirc = strdup(path); basec = strdup(path); dname = dirname(dirc); bname = basename(basec); printf("dirname=%s, basename=%s\n", dname, bname); free(dirc); free(basec);
Both dirname and basename return pointers to null-terminated strings.
In versions of glibc up to and including 2.2.1, dirname does not correctly handle pathnames with trailing '/' characters, and generates a segmentation violation if given a NULL argument.
char *mybasename(char *x) {
if (!x)
return x;
return strrchr(x) ? strrchr(x)+1 : x;
}
if this is listed as being static then the compiler should do a nice job of optimising this.
One page links to basename(3):