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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=56993 --- shadow/56993 2005-06-29 06:43:09.000000000 -0400 +++ shadow/56993.tmp.20727 2005-06-29 07:25:52.000000000 -0400 @@ -129,6 +129,21 @@ You can (and should) use Path.PathSeparator instead of \ or / when building paths without Path.Combine. ------- Additional Comments From [EMAIL PROTECTED] 2005-06-29 06:43 ------- I don't think wishlist items should be closed as NOTABUG + +------- Additional Comments From [EMAIL PROTECTED] 2005-06-29 07:25 ------- +Then please close it as you wish but this feature should not be +implemented because it would cause problems. For example on +Linux '\' is a valid charachter in file and directory names. By +replacing '\' to '/' the runtime could even cause security problems +by accessing to different files it should. And the current path +model is compatible even with an imaginary files system where +both '\' and '/' are valid characters and path separator is 'X' for +example. By implementing '\' to '/' conversion applications would +use '\' as path separator instead of Path.PathSeparator and they +could not access to files containing '\' in their names. Class +Library has to provide transparent path handling to operating system +functions. System.IO.Path is intended to expose the characteristics +of paths and implement path handling functionality. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
