Yahoo India Web Search

Search results

  1. Mar 14, 2014 · 12. IMHO, this is the most important reason: String is Immutable in Java because String objects are cached in String pool. Since cached String literals are shared between multiple clients there is always a risk, where one client's action would affect all another client. Ref: Why String is Immutable or Final in Java.

  2. Jan 10, 2012 · String is immutable ( once created can not be changed ) object . The object created as a String is stored in the Constant String Pool. Every immutable object in Java is thread safe ,that implies String is also thread safe . String can not be used by two threads simultaneously. String once assigned can not be changed.

  3. String class is immutable, and you can not change value of immutable object. But in case of String, if you change the value of string than it will create new string in string pool and than your string reference to that value not the older one. so by this way string is immutable. Lets take your example, String str = "Mississippi"; System.out ...

  4. Jun 8, 2014 · There are a couple of minor downsides for immutable types: Operations that create a changed string like concatenation are more expensive because you need to construct new objects. Typically the cost is O (n+m) for concatenating two immutable Strings, though it can go as low as O (log (m+n)) if you use a tree-based string data structure like a ...

  5. Aug 5, 2014 · 0. Mutable means you will save the same reference to variable and change its contents but immutable you can not change contents but you will declare new reference contains the new and the old value of the variable. Ex Immutable -> String. String x = "value0ne";// adresse one.

  6. Sep 18, 2008 · And to address the same issue of these String literals being modified at runtime, Java simply makes the String class immutable (i. e, gives you no setters that would allow you to change the String content). Strings would not have to be immutable if interning of String literals did not occur.

  7. Jan 6, 2014 · So, in "reality", no they are not absolutely immutable. To point 2: This is because substring is probably allocating a new string instance, which is likely copying the array. It is possible to implement substring in such a way that it won't do a copy, but that doesn't mean it does. There are tradeoffs involved.

  8. Sep 22, 2010 · 1. One of the reasons for the "need" for immutable classes is the combination of passing everything by reference and having no support for read-only views of an object (i.e. C++'s const). Consider the simple case of a class having support for the observer pattern: public string getName() { ...

  9. Mar 28, 2012 · 8. Because Strings are immutable, to manipulate Strings, such as to concatenate Strings, you have to create new String objects, since obviously, you can't change the state of existing String objects. Whereas with a StringBuffer or StringBuilder, you create one object and simply change its state. If you're doing some major String concatenation ...

  10. Nov 11, 2008 · Immutable means that once the object is created, non of its members will change. String is immutable since you can not change its content. For example: String s1 = " abc "; String s2 = s1.trim (); In the code above, the string s1 did not change, another object (s2) was created using s1. Share.

  1. People also search for