Boolean construction(new/valueOf) - why different result?

[Alton Hernandez]

Since a Boolean object can only have two values (true or false), and since there already exists the Boolean objects TRUE and FALSE, then why is everytime a boolean object is created using its constructor, a new object is created? Why not just do it the way the valueOf method does it - return a reference to Boolean.TRUE or Boolean.FALSE?

class D {
  public static void main (String[] args) {
    Boolean b1 = Boolean.valueOf("trUE");          // 1
    Boolean b2 = Boolean.valueOf("Very True");     // 2
    Boolean b3 = Boolean.valueOf(null);            // 3
    System.out.print((b1==b2) + ",");
    System.out.print((b2==b3) + ",");
    System.out.println(b3==b1);

    b1 = new Boolean("trUE");              //4
    b2 = new Boolean("Very True");         //5
    b3 = new Boolean(null);                //6
    System.out.print((b1==b2) + ",");
    System.out.print((b2==b3) + ",");
    System.out.println(b3==b1);
  }
}

[B]Result:[/B]
false,true,false
false,false,false

[Miki Muzsi]

I think the idea of "new" is to create new objects. If you would want to have the same object than it should be the same with strings as well. Why new String("aaa") creates an obejct (ok, actually two with the string literal) and new String("aaa") create another object. And they are different one.

Miki

[Damien Howard]

new actually creates a new object regardless, but if you do String="aaa"; then it will check the String pool and use the same object if it exists. Don't know why Java was designed like this, but it is.

[Alton Hernandez]

Yes, that's probably the reason.
I now realize that there are economical ways of creating objects. I guess this is one of the benefits when you study for SCJP.
Thanks.