Win32's PathResolve is resolving \temp into c:\temp, even if I run the function from another drive.
In addition, IsRelative() returns false for '\temp' - which makes me wonder what kind of resolution it actually thinks it's doing for this path.
views:
58answers:
1When? The way I see it paths are always evaluated in the context of a running process which always has a working directory. What sort of API function, when run from a process that has a working directory in D:\SomeDir, interprets a path such as "\temp" to mean "C:\temp"?I just don't get it.
Assaf Lavie
2010-05-04 19:20:09
Well, http://msdn.microsoft.com/en-us/library/bb776478%28VS.85%29.aspx speaks of "unqualified" paths, of which I think "\temp" would be a member. My guess is that it expands unqualified paths to the "root device", which is your system drive, and turns up as "C:\temp". If you need to expand it relative to the working directory, you will probably need to use just that, a _relative_ path, such as "temp".
Jens Björnhager
2010-05-05 05:48:21
That's inconsistent with the CombinePaths function that takes d:\dir and \otherDir and produces d:\otherDir.
Assaf Lavie
2010-05-05 09:29:10
Cant find any win32 function with that name. Are you using .net?
Jens Björnhager
2010-05-05 15:57:29
Sorry, I meant PathCombine: http://msdn.microsoft.com/en-us/library/bb773571(v=VS.85).aspx
Assaf Lavie
2010-05-27 09:30:42
Well, in PathCombine you explicitly state the drive. It seems that the path needs to begin with a driver letter: "The directory path should be in the form of A:,B:, ..., Z:."
Jens Björnhager
2010-05-27 15:00:00