May 25, 20169 yr First of all, you should avoid calling obj == other except for null comparison. Ehm, no. Agreed with everything else you said, but this is not true. Yeah, I was more in the 'teach java' mode than I should have been in the context of minecraft and forge. I was thinking about the comparison of general objects, the obj == oObj operator, as you probably know, checks whether the obj and oObj are actually the *same* object, pointing to the same memory part. While .equals() (if properly overwritten) checks if the objects do have the same properties. My apologies for this. Sincerely -pick Since English is not my mother tongue, my sentences may are confusing. I'm coding java for a long time now - just MC and forge stop me sometimes.
May 25, 20169 yr First of all, you should avoid calling obj == other except for null comparison. Ehm, no. Agreed with everything else you said, but this is not true. Yeah, I was more in the 'teach java' mode than I should have been in the context of minecraft and forge. I was thinking about the comparison of general objects, the obj == oObj operator, as you probably know, checks whether the obj and oObj are actually the *same* object, pointing to the same memory part. While .equals() (if properly overwritten) checks if the objects do have the same properties. My apologies for this. Sincerely -pick Since English is not my mother tongue, my sentences may are confusing. I'm coding java for a long time now - just MC and forge stop me sometimes.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.