equality-operator

This question already has an answer here: Why isn't [1,2,3] equal to itself in Javascript? 6 answers Why is [] !== [] in JavaScript? I read through https://developer.mozilla.org/en-US/docs/Web/JavaScript/Equality_comparisons_and_sameness but I could not find anything that explains this. Edit: I don't think this question or this question is an exact duplicate of mine. It asks about the == operator which just behaves crazy. The answer is an answer to my question but it's not the same question. That does a reference check on the two array literals to see if they are the same instance. The fact

I am developing an application in Android using Eclipse. I wrote the following code and in tests the first and third " if " block is not reachable. Why? When I add a leading zero to a number, the equal operator returns false. int var = 123; if (var == 0123) { //not reachable } if (var == 123) { //reachable } if (var == (int)0123) { //not reachable } if (var == (int)123) { //reachable } 0123 is an octal number ( leading 0 ), while 123 is a decimal number. so 0123 actually equals to 83. Any integer Number Leading With Zero is octal Number (base 8). 0123 is octal Number and 123 is Decimal Number

A few weeks ago, I have read this thread Is < faster than <=? about comparison operators in C . It was said that there is no difference in the performance between < and <= as they are interpreted as same/similar machine commands. At the same time, in our company's "best practices", it was said that we should always use "===" to compare things instead of "==". So, I started to wonder if this is always appropriate as I am used to using the "==" and "typeof ... == " and do not want to change my way of writing :-] Note that this is in the context of JavaScript. So, I have a little research and