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 was looking at some example C++ code for a hardware interface I’m working with and noticed a lot of statements along the following lines:
if ( NULL == pMsg ) return rv;
I’m sure I’ve heard people say that putting the constant first is a good idea, but why is that? Is it just so that if you have a large statement you can quickly see what you’re comparing against or is there more to it?
So that you don’t mix comparison (==) with assignment (=).
As you know, you can’t assign to a constant. If you try, the compiler will give you an error.
Basically, it’s one of defensive programming techniques. To protect yourself from yourself.