Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Some POSIX functions are not threadsafe. Examples are dirname and pathname.
The dirname() function need not be reentrant. A function that is not required to be reentrant is not required to be thread-safe.
On some platforms there are reentrant versions of dirname and pathname: dirname_r and pathname_r.
As far as I found out there are not reentrant version of dirname and pathname on Linux.
I’m not aware of reentrant versions of
dirnameandbasenamein Linux.However, there’s various reentrant implementations of both functions in different non-standard libraries.
g_path_get_dirname and g_path_get_basename from glib are probably commonly used, and their implementation doesn’t depend too much on the rest of the glib library either, so it’d be easy enough to just borrow from their implementation if you don’t particularly feel like linking against glib.