Re: Backing Up Objects

From:

Lew <lew@lewscanon.nospam>

Newsgroups:

comp.lang.java.programmer

Date:

Mon, 09 Jul 2007 19:53:58 -0400

Message-ID:

<na2dnXI7bIIKVw_bnZ2dnUVZ_hadnZ2d@comcast.com>

Hal Vaughan writes:

String newString = oldString;

that newString is simply a pointer to oldString so if I change the
value in
one, I change the value in the other.

Lew wrote:

Ironically, under most circumstances it is not possible to change the
value of a String, so this made a bad example. Strings are
"immutable"; without resorting to evil reflection trickery their value
cannot be changed after construction. An example using "Foo" instead
of "String" would be valid (one would assume Foo is not immutable).

Piotr Kobzda wrote:

One would assume "String" is mutable:

  public class String {
    public java.lang.String value;
    public java.lang.String toString() { return value; }
  }

You're just being argumentative.

Absent any specific disclaimer to the contrary, as the original post was, why
in the world would one figure that "String" meant anything other than
"java.lang.String"? If you wish to assume the OP is an idiot who reuses the
most fundamental class names, thus damaging maintenance, then perhaps, and
only perhaps, your point would have a micro-skootch of merit, but I refuse to
believe the OP was that stupid.

Be real.

--
Lew