我在不可变字符串上写了下面的代码。
public class ImmutableStrings {
public static void main(String[] args) {
testmethod();
}
private static void testmethod() {
String a = "a";
System.out.println("a 1-->" + a);
a = "ty";
System.out.println("a 2-->" + a);
}
}
输出:
a 1-->a
a 2-->ty
这里变量a的值被改变了(尽管许多人说不可变对象的内容不能被改变)。但是说字符串是不可变的到底是什么意思呢?你能给我解释一下这个话题吗?
来源:https://docs.oracle.com/javase/tutorial/java/nutsandbolts/datatypes.html
当前回答
字符串是不可变的，这意味着，字符串对象的内容不能被改变，一旦它被创建。如果你想修改内容，那么你可以去StringBuffer/StringBuilder而不是String。StringBuffer和StringBuilder是可变类。
其他回答
我认为下面的代码可以明确区别:
String A = new String("Venugopal");
String B = A;
A = A +"mitul";
System.out.println("A is " + A);
System.out.println("B is " + B);
StringBuffer SA = new StringBuffer("Venugopal");
StringBuffer SB = SA;
SA = SA.append("mitul");
System.out.println("SA is " + SA);
System.out.println("SB is " + SB);
String S1="abc";
S1.concat("xyz");
System.out.println("S1 is", + S1);
String S2=S1.concat("def");
System.out.println("S2 is", + S2);
这表明一旦创建了一个字符串对象，它就不能被更改。每次你需要创建new并放入另一个String。年代
在这里看到的
class ImmutableStrings {
public static void main(String[] args) {
testmethod();
}
private static void testmethod() {
String a="a";
System.out.println("a 1-->"+a);
System.out.println("a 1 address-->"+a.hashCode());
a = "ty";
System.out.println("a 2-->"+a);
System.out.println("a 2 address-->"+a.hashCode());
}
}
输出:
a 1-->a
a 1 address-->97
a 2-->ty
a 2 address-->3717
这表明无论何时修改不可变字符串对象a的内容都会创建一个新对象。也就是说，你不允许改变不可变对象的内容。这就是为什么两个对象的地址是不同的。
你不是在改变赋值语句中的对象，而是用另一个不可变对象替换了一个不可变对象。Object String("a")不会变成String("ty")，它会被丢弃，对ty的引用会被写入a中。
相反，StringBuffer表示一个可变对象。你可以这样做:
StringBuffer b = new StringBuffer("Hello");
System.out.writeln(b);
b.append(", world!");
System.out.writeln(b);
在这里，您没有重新分配b:它仍然指向相同的对象，但该对象的内容已经更改。
If some object bar holds a reference to a mutable object foo and encapsulates some of its state in mutable aspects of foo's state, that will allow code which can change those aspects of foo to change the corresponding aspects of bar's state without actually touching bar or even knowing of its existence. Generally, this means that objects which encapsulate their own state using mutable objects must ensure that no references to those objects are exposed to any code which might unexpectedly mutate them. By contrast, if bar holds a reference to an object moo and only uses immutable aspects of moo other than identity to encapsulate its state, then bar can freely expose moo to outside code without worrying about anything the outside code might do to it.
