What are these dire multithreading consequences that the GetFullPathName documentation is trying to warn me about?

The documentation for the Get­Full­Path­Name function contains this dire warning: Multithreaded applications and shared library code should not use the GetFullPathName function and should avoid using relative path names. The current directory state written by the SetCurrentDirectory function is stored as a global variable in each process, The post What are these dire multithreading consequences that the GetFullPathName documentation is trying to warn me about? appeared first on The Old New Thing...

Submit