[Mono-bugs] [Bug 74771][Maj] Changed - System.Path.IO is no longer handling Windows like paths.
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Fri, 29 Apr 2005 19:35:01 -0400 (EDT)
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 rlyon@novell.com.
http://bugzilla.ximian.com/show_bug.cgi?id=74771
--- shadow/74771 2005-04-29 18:31:48.000000000 -0400
+++ shadow/74771.tmp.15308 2005-04-29 19:35:01.000000000 -0400
@@ -42,6 +42,30 @@
echo > "c:\\test\\test.txt"
To witness
Miguel.
+
+------- Additional Comments From rlyon@novell.com 2005-04-29 19:35 -------
+I can work around this, but I think it will cause problems for users
+in the future.
+
+I understand Mono to include a virtual machine that I can run
+applications that have been targeted to .NET. I read that both the
+Path.DirectorySeparatorChar and the Path.AltDirectorySeparatorChar
+are both valid for separating directory levels in a path string and
+that the value of Path.AltDirectorySeparatorChar "... is a backslash
+('\') on Unix, and a slash ('/') on Windows and Macintosh operating
+systems."
+
+Applications that work with Unix and Windows file paths (which will
+include any web application that uses an HTML Form with a file input
+type), will have to be modified to work with Mono.
+
+While you can create a file like "c:\test\test.txt" on Unix it is
+not a valid name in .Net or in Java for that matter (even on Linux).
+And it should be possible to work with that file, but it should be
+translated into the VM, not the VM molded around it.
+
+Why limit the VM and break compatibilty just because the underlying
+OS supports something differently?