From 226ac347c51e21440d1740d85b5e9912d1ce08e5 Mon Sep 17 00:00:00 2001 From: "B. Stack" Date: Mon, 6 Dec 2021 07:57:52 -0500 Subject: add upstream 11.15 --- zen/resolve_path.cpp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'zen/resolve_path.cpp') diff --git a/zen/resolve_path.cpp b/zen/resolve_path.cpp index 4eab76ee..0a45646e 100644 --- a/zen/resolve_path.cpp +++ b/zen/resolve_path.cpp @@ -8,6 +8,7 @@ #include "time.h" #include "thread.h" #include "file_access.h" +#include "file_path.h" #include //getenv() #include //getcwd() @@ -44,7 +45,7 @@ Zstring resolveRelativePath(const Zstring& relativePath) assert(runningOnMainThread()); /* MSDN: "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, + SetCurrentDirectory function is stored as a global variable in each process, therefore multithreaded applications cannot reliably use this value without possible data corruption from other threads, [...]" => Just plain wrong, there is no data corruption. What MSDN really means: GetFullPathName() is *perfectly* thread-safe, but depends -- cgit