[Mono-bugs] [Bug 80737][Nor] Changed - Path.GetFullPath returns wrong results if mixing "/" and "\"

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Feb 6 10:16:41 EST 2007

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by frederik.carlier at ugent.be.


--- shadow/80737	2007-02-06 10:04:35.000000000 -0500
+++ shadow/80737.tmp.27408	2007-02-06 10:16:41.000000000 -0500
@@ -100,6 +100,26 @@
 fcarlier at col-clt-04:~/monobug/IOTest$ mono IOTest.exe 
 basePath: /home/fcarlier/myproject/Properties
 relativePath: ..\Resources\myfile.png
 combinedPath: /home/fcarlier/myproject/Properties/..\Resources\myfile.png
 fullPath: /home/fcarlier/myproject/Properties/..\Resources\myfile.png
+------- Additional Comments From frederik.carlier at ugent.be  2007-02-06 10:16 -------
+One last remark. The ECMA specs say the same, that "/" and "\" are
+equivalent. Hence, I think in some way you should see the Linux paths
+containing "\" incompatible with the ECMA specs, and not the other way
+Therefore, in my opinion, Mono's default behaviour (if it is to adhere
+to the specs) should be to support "\" as a directory separator. That
+means that linux file names containing "\" are incompatible with Mono. 
+Then, if somebody would like to use "\" as part of a file name, it's
+up to them to invoke a compatibility layer.
+Hardcoding "\" as a directory separator, as referred to in the
+MONO_IOMAP documentation, is not bad design, but 100% compatible with
+the specs.
+I was looking for background information on MONO_IOMAP (as to see what
+arguments were raised for the current implementation), but couldn't
+find it. Hence, if I'm repeating arguments, I'm sorry.

More information about the mono-bugs mailing list