Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Does concatenating strings in Java always lead to new strings being created in memory?

I have a long string that doesn't fit the width of the screen. For eg.

String longString = "This string is very long. It does not fit the width of the screen. So you have to scroll horizontally to read the whole string. This is very inconvenient indeed.";

To make it easier to read, I thought of writing it this way -

String longString = "This string is very long." + 
                    "It does not fit the width of the screen." +
                    "So you have to scroll horizontally" +
                    "to read the whole string." +
                    "This is very inconvenient indeed.";

However, I realized that the second way uses string concatenation and will create 5 new strings in memory and this might lead to a performance hit. Is this the case? Or would the compiler be smart enough to figure out that all I need is really a single string? How could I avoid doing this?

like image 204
CodeBlue Avatar asked Aug 16 '12 14:08

CodeBlue


People also ask

Does string concatenation create a new string in Java?

Since the String object is immutable, each call for concatenation will result in a new String object being created.

What happens when we concatenate a string in Java?

Concatenating Strings Using the concat() method − The concat() method of the String class accepts a String value, adds it to the current String and returns the concatenated value.

What happens when concatenating strings?

Concatenation is the process of appending one string to the end of another string. You concatenate strings by using the + operator. For string literals and string constants, concatenation occurs at compile time; no run-time concatenation occurs. For string variables, concatenation occurs only at run time.

Does concat create a new object in Java?

The concat method would create new string object as output after appending only if output string has length greater than zero otherwise return the same target string as an output object. + operator always create new object as output no matter what length of result string produced after appending.


2 Answers

I realized that the second way uses string concatenation and will create 5 new strings in memory and this might lead to a performance hit.

No it won't. Since these are string literals, they will be evaluated at compile time and only one string will be created. This is defined in the Java Language Specification #3.10.5:

A long string literal can always be broken up into shorter pieces and written as a (possibly parenthesized) expression using the string concatenation operator +
[...]
Moreover, a string literal always refers to the same instance of class String.

  • Strings computed by constant expressions (§15.28) are computed at compile time and then treated as if they were literals.
  • Strings computed by concatenation at run-time are newly created and therefore distinct.

Test:

public static void main(String[] args) throws Exception {     String longString = "This string is very long.";     String other = "This string" + " is " + "very long.";      System.out.println(longString == other); //prints true } 

However, the situation situation below is different, because it uses a variable - now there is a concatenation and several strings are created:

public static void main(String[] args) throws Exception {     String longString = "This string is very long.";     String is = " is ";     String other = "This string" + is + "very long.";      System.out.println(longString == other); //prints false } 
like image 95
assylias Avatar answered Sep 26 '22 23:09

assylias


Does concatenating strings in Java always lead to new strings being created in memory?

No, it does not always do that.

If the concatenation is a compile-time constant expression, then it is performed by the compiler, and the resulting String is added to the compiled classes constant pool. At runtime, the value of the expression is the interned String that corresponds to the constant pool entry.

This will happen in the example in your question.

like image 35
Stephen C Avatar answered Sep 25 '22 23:09

Stephen C