[Mono-bugs] [Bug 40557][Min] Changed - square brackets and braces cause Directory.cs methods to act incorrectly

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 5 Apr 2004 06:51:54 -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 dick@ximian.com.


--- shadow/40557	2003-08-04 18:04:22.000000000 -0400
+++ shadow/40557.tmp.882	2004-04-05 06:51:54.000000000 -0400
@@ -1,8 +1,8 @@
 Bug#: 40557
-Product: Mono/Class Libraries
+Product: Mono: Class Libraries
 Version: unspecified
 OS: other
 OS Details: Gentoo 1.4rc3
 Status: NEW   
 Severity: Unknown
@@ -63,6 +63,35 @@
 mono/mono/io-layer/io.c uses the glob(7) function to parse the
 pattern.  glob accepts three wild cards *, ?, and brackets (character
 classes).  It's unclear what the desired functionality of pattern
 matching should be.  If it is to correspond to Win32 pattern matching,
 then all brackets should be escaped.  Otherwise, the behavior is
 correct, and it's up to the user to do her own escaping.
+------- Additional Comments From drteeth@monkeyhouse.ca  2003-08-11 18:17 -------
+Created an attachment (id=5098)
+source for the test case
+------- Additional Comments From drteeth@monkeyhouse.ca  2003-08-11 18:18 -------
+i'm not sure what you mean.  How would i escape the brackets?
+escaping the brackets in code like this:
+args[0].Replace( "[", "\\[" ).Replace( "]", "\\]" ) 
+results gives:
+DirectoryNotFoundException: Directory '\[testdir\]' not found.
+..which makes sense to me.  
+I don't see how this behavior is correct, as i can't seem to find a 
+way to list the contents of a folder with bracket's in the name.  
+using DirectoryInfo doesn't seem to help either, as you can see in 
+the example attached.
+------- Additional Comments From drteeth@monkeyhouse.ca  2003-08-11 18:20 -------
+Created an attachment (id=5099)
+shell script to setup up the test case, attached above
+------- Additional Comments From dick@ximian.com  2004-04-05 06:51 -------
+*** Bug 56424 has been marked as a duplicate of this bug. ***