Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I just found out that I can compare null with an Object like this,
if(null != Object)
Rather than comparing Object with null, like
Object != null
What may go wrong if use the former approach?
Is that legal? If not then why does compiler accept it?
There’s one thing wrong about it – readability. If you want to write a clean code, you should care about the way it will be read in the future. It needs to be obvious, what it does and why it does a certain thing. If you place the “Object” to the right of the evaluation, it becomes less apparent what are you really doing. Well at least in my opinion…