30

I recently noticed that, String.replaceAll(regex,replacement) behaves very weirdly when it comes to the escape-character "\"(slash)

For example consider there is a string with filepath - String text = "E:\\dummypath" and we want to replace the "\\" with "/".

text.replace("\\","/") gives the output "E:/dummypath" whereas text.replaceAll("\\","/") raises the exception java.util.regex.PatternSyntaxException.

If we want to implement the same functionality with replaceAll() we need to write it as, text.replaceAll("\\\\","/")

One notable difference is replaceAll() has its arguments as reg-ex whereas replace() has arguments character-sequence!

But text.replaceAll("\n","/") works exactly the same as its char-sequence equivalent text.replace("\n","/")

Digging Deeper: Even more weird behaviors can be observed when we try some other inputs.

Lets assign text="Hello\nWorld\n"

Now, text.replaceAll("\n","/"), text.replaceAll("\\n","/"), text.replaceAll("\\\n","/") all these three gives the same output Hello/World/

Java had really messed up with the reg-ex in its best possible way I feel! No other language seems to have these playful behaviors in reg-ex. Any specific reason, why Java messed up like this?

shmosel
  • 49,289
  • 6
  • 73
  • 138
Bharath
  • 543
  • 1
  • 6
  • 11

6 Answers6

28

You need to esacpe twice, once for Java, once for the regex.

Java code is

"\\\\"

makes a regex string of

"\\" - two chars

but the regex needs an escape too so it turns into

\ - one symbol
Sotirios Delimanolis
  • 274,122
  • 60
  • 696
  • 724
Peter Lawrey
  • 525,659
  • 79
  • 751
  • 1,130
  • 1
    Escape twice? Once for Java and Once for regex? Then by the same logic, can you explain me why, `text.replaceAll("\n","/"), text.replaceAll("\\n","/"), text.replaceAll("\\\n","/")` all these give the same output. Where does the escape twice once for java and once for regex logic go there? – Bharath Sep 18 '13 at 16:47
  • 2
    `\n` is plain newline character, this conversion is at compile time. `\\n` tells the regex Pattern processors to decode the newline, something it does at runtime. The `\\\n` means take the `\n` as a literal. This ends up being the same thing in a more complicated way. The reason there are multiple ways of doing this, is that the `\\` is supported for all literal characters and just happens to work for characters which are taken literally anyway. – Peter Lawrey Sep 18 '13 at 17:19
  • Yeah I understand now, particularly after Stephen's answer :) Thanks a lot for the help :) – Bharath Sep 19 '13 at 11:49
25

@Peter Lawrey's answer describes the mechanics. The "problem" is that backslash is an escape character in both Java string literals, and in the mini-language of regexes. So when you use a string literal to represent a regex, there are two sets of escaping to consider ... depending on what you want the regex to mean.

But why is it like that?

It is a historical thing. Java originally didn't have regexes at all. The syntax rules for Java String literals were borrowed from C / C++, which also didn't have built-in regex support. Awkwardness of double escaping didn't become apparent in Java until they added regex support in the form of the Pattern class ... in Java 1.4.

So how do other languages manage to avoid this?

They do it by providing direct or indirect syntactic support for regexes in the programming language itself. For instance, in Perl, Ruby, Javascript and many other languages, there is a syntax for patterns / regexs (e.g. '/pattern/') where string literal escaping rules do not apply. In C# and Python, they provide an alternative "raw" string literal syntax in which backslashes are not escapes. (But note that if you use the normal C# / Python string syntax, you have the Java problem of double escaping.)


Why do text.replaceAll("\n","/"), text.replaceAll("\\n","/"), and text.replaceAll("\\\n","/") all give the same output?

The first case is a newline character at the String level. The Java regex language treats all non-special characters as matching themselves.

The second case is a backslash followed by an "n" at the String level. The Java regex language interprets a backslash followed by an "n" as a newline.

The final case is a backslash followed by a newline character at the String level. The Java regex language doesn't recognize this as a specific (regex) escape sequence. However in the regex language, a backslash followed by any non-alphabetic character means the latter character. So, a backslash followed by a newline character ... means the same thing as a newline.

Stephen C
  • 698,415
  • 94
  • 811
  • 1,216
7

1) Let's say you want to replace a single \ using Java's replaceAll method:

   \
   ˪--- 1) the final backslash

2) Java's replaceAll method takes a regex as first argument. In a regex literal, \ has a special meaning, e.g. in \d which is a shortcut for [0-9] (any digit). The way to escape a metachar in a regex literal is to precede it with a \, which leads to:

 \ \
 | ˪--- 1) the final backslash
 |
 ˪----- 2) the backslash needed to escape 1) in a regex literal

3) In Java, there is no regex literal: you write a regex in a string literal (unlike JavaScript for example, where you can write /\d+/). But in a string literal, \ also has a special meaning, e.g. in \n (a new line) or \t (a tab). The way to escape a metachar in a string literal is to precede it with a \, which leads to:

\\\\
|||˪--- 1) the final backslash
||˪---- 3) the backslash needed to escape 1) in a string literal
|˪----- 2) the backslash needed to escape 1) in a regex literal
˪------ 3) the backslash needed to escape 2) in a string literal
sp00m
  • 47,968
  • 31
  • 142
  • 252
  • 1
    I think this is an awesome answer, which clearly explains what is going on behind the scenes. Surprising that I am first upvoter ! – HopeKing Mar 01 '18 at 04:29
-2

This is because Java tries to give \ a special meaning in the replacement string, so that \$ will be a literal $ sign, but in the process they seem to have removed the actual special meaning of \

While text.replaceAll("\\\\","/"), at least can be considered to be okay in some sense (though it itself is not absolutely right), all the three executions, text.replaceAll("\n","/"), text.replaceAll("\\n","/"), text.replaceAll("\\\n","/") giving same output seem even more funny. It is just contradicting as to why they have restricted the functioning of text.replaceAll("\\","/") for the same reason.

Java didn't mess up with regular expressions. It is because, Java likes to mess up with coders by trying to do something unique and different, when it is not at all required.

coder91
  • 51
  • 3
  • 3
    The behavior you're talking about is not incorrect, it's merely inconvenient. If you understand the escaping rules for string literals and regexes, it makes perfect sense. It might have been better if they had used `$$` (like the .NET flavor does) instead of `\$` to escape dollar signs in the replacement string, but the current design is not broken. – Alan Moore Sep 18 '13 at 20:25
  • 1
    you are right. I dint understand earlier before Stephen's answer, that they had to do it this way because, "reg-ex" were written latter and "\" has special meaning in string literals before that itself and hence the double-escaping. Now I understand the escaping rules of both string literals and regexes, and it makes perfect sense :) – coder91 Sep 19 '13 at 11:48
-3

One way around this problem is to replace backslash with another character, use that stand-in character for intermediate replacements, then convert it back into backslash at the end. For example, to convert "\r\n" to "\n":

String out = in.replace('\\','@').replaceAll("@r@n","@n").replace('@','\\');

Of course, that won't work very well if you choose a replacement character that can occur in the input string.

MTaylorEx
  • 55
  • 1
  • 1
  • 4
-4

I think java really messed with regular expression in String.replaceAll();

Other than java I have never seen a language parse regular expression this way. You will be confused if you have used regex in some other languages.

In case of using the "\\" in replacement string, you can use java.util.regex.Matcher.quoteReplacement(String)

String.replaceAll("/", Matcher.quoteReplacement("\\"));

By using this Matcher class you can get the expected result.

Pshemo
  • 122,468
  • 25
  • 185
  • 269
Rajagopal
  • 139
  • 1
  • 8
  • 1
    `quoteReplacement()` is meant to be used on the replacement string, which is the *second* argument. The first argument is the regex, and to escape it you use `java.util.regex.Pattern.quote(String)`. – Alan Moore Sep 18 '13 at 19:52