[Mono-bugs] [Bug 58256][Wis] Changed - Replace Doesn't Replace ' Correctly

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 13 May 2004 03:03:09 -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 kjambunathan@novell.com.

http://bugzilla.ximian.com/show_bug.cgi?id=58256

--- shadow/58256	2004-05-13 02:40:46.000000000 -0400
+++ shadow/58256.tmp.15876	2004-05-13 03:03:09.000000000 -0400
@@ -49,6 +49,35 @@
 
 On MS .NET, Escape Sequences are <\a\b\t\r\f\n\e\040\x20\cC\u0020
 \\\'>.On MS .NET, Escape Sequences don't work.But substitution does 
 work.
 
 
+
+------- Additional Comments From kjambunathan@novell.com  2004-05-13 03:03 -------
+On my Linux box I get:
+
+On MS .NET, Escape Sequences are <\\\\\\\\40\20\C\0020\\>.On MS .NET,
+Escape Sequences don't work.But substitution does work.
+
+So this is where I stand wrt the above issue:
+
+1) Microsoft honors only the substitution meta characters in the
+replacement pattern. All other characters are used verbatim.
+
+This behaviour is not in agreement with the documentation which claims
+
+"Character escapes and substitutions are the only special constructs
+recognized in a replacement pattern".
+
+2) On Linux boxes, we "try" to unescape the string before creating the
+ultimate replacement string. But there is a bug in our implementation.
+So the above meaningless output with the Linux box.
+
+Should we take up this issue as a bug in implementation with Microsoft
+or should we make our implementation compatible with current
+Microsoft's implementation is a question that might have to be answered. 
+
+Anyway on Linux, our implemetation is different from our intent. Will
+attach a patch soon.
+
+