Timeline for Implementing dirpath(3p) and fdirpath(3p) functions
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2015 at 21:25 | comment | added | ghostmansd |
What do you think about just using mutexes? That's the first idea that came to my mind, but I also wanted to try to avoid situations where someone else is calling chdir.
|
|
| Feb 19, 2015 at 21:22 | comment | added | ghostmansd |
What's an amazing post! Thank you very much, I've never thought about such kind of problems. Well, actually functions can use platform-dependent solutions (e.g. readlink on /proc/PID/fd/XXX on Linux and Cygwin, F_GETPATH for OS X, etc.) and then fallback to current behaviour. However, on mentioned systems there are already *at() calls, if I recall correctly. Actually neither I think that using mmap with the real file is a good idea. The only reason why I do it is that POSIX doesn't support MAP_ANON (there is a proposal to bring this flag in the next standard though).
|
|
| Feb 19, 2015 at 21:01 | history | answered | vnp | CC BY-SA 3.0 |