[Mono-bugs] [Bug 58256][Nor] Changed - [PATCH] Replace Doesn't Replace ' Correctly
Fri, 14 May 2004 02:02:11 -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 firstname.lastname@example.org.
--- shadow/58256 2004-05-14 00:59:44.000000000 -0400
+++ shadow/58256.tmp.1677 2004-05-14 02:02:11.000000000 -0400
@@ -102,6 +102,22 @@
Patch for Original Bug 58256
------- Additional Comments From email@example.com 2004-05-13 10:32 -------
Parse Escape is not handling the following Escape Sequences \b and
\*(say ). I am an attaching a patch for the same as well.
+------- Additional Comments From firstname.lastname@example.org 2004-05-14 02:02 -------
+According to the MS documentation:
+"In a regular expression, \b denotes a word boundary (between \w and
+\W characters) except within a  character class, where \b refers to
+the backspace character. In a replacement pattern, \b always denotes a
+Initially, I suspected that a trivial modification to ParseEscape()
+will suffice. Later I realised that \b is handled differently based
+upon the context. I need to investigate whether the obvious
+modiifcation to ParseEscape() will create unwanted side-effects wrt to
+parsing of \b in other contexts.