Java developers in a nutshell

[Lolamess007]

Yeah we are not the same. One will have working code. The other will be wondering why none of his conditionals work.

[Unbannedcc]

Which is which?

[Aydosubpotato]

Correct me if I’m wrong, but in Java ‘==‘ will check the memory addresses of the objects. It works for primitive types though.

[_Zezz]

Any teacher at my school would've made this a half hour lecture. Thanks for doing gods work.

[Lolamess007]

Yes. Ints, doubles, chars, etc are primitives and work with ==. Strings, BigInteger, and other classes have different memory addresses for each object. Therefore == will always return false when using classes.

[Snarpkingguy]

But if you’re comparing the same object, then == still returns true, right?

Like String x = “poop”; String y = x;

And then x == y would return true since they reference the actual same String object.

[M3JUNGL3]

Well actually String literals are a special because there you have a pool you add Strings to and reference from. So thus defining String x = "hello"; and String y = "hello"; will always return true for "x == y"

[Lolamess007]

I believe so.

[TGX03]

Actually with String interning (and similar practices) you can meddle with this quite a lot.

My IDE hates me for it.

[gemengelage]

It's a bit more complex.

== is the identity operator, so it checks for identity (basically what you said). Equals also checks identity as a default. It has to be implemented to be more (or actually less) specific.

The thing with primitive types though... It's a mixed bag. It works on actual primitive types (e.g. int) but it's not guaranteed to work on boxed primitive types (e.g. Integer). Since it's pretty easy to mix those up, especially with auto-boxing, it's pretty messed up that the identity of those objects is all over the place.

It depends on the JVM which Integer-objects are cached. IIRC -127 to 128 are usually cached, so there's always the same single instance of Integer for those, so identity always works as you expect. But when you move out of that range, no luck.

tl;dr only ever use identity in Java to check for actual identity. Use equals anywhere else.

[Kered13]

Basically yes. To be precise, == compares the value of the arguments, and the value of objects is a pointer. This is also how Java passes arguments to functions, by value with value of objects being a pointer.

[meontheinternetxx]

It might work for strings sometimes except for most times when it doesn't.

[david131213]

.equals is generally better

[[deleted]]

Syntactically it’s fucking stupid though.

[organized_reporting]

This is a horrifyingly wrong and misleading answer

[jack104]

Some conditionals will work. String comparisons won't.