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.
for(unsigned int i = 0; i < x.size(); i++)
assert(x[i] > 0);
When not debugging (NDEBUG flag), the resultant is an empty for loop. Is there a clean way to handle this (not executing the empty for loop); preferably without preprocessor directive, since it would defeat the purpose of assert in the first place.
A good optimizer should be able to eliminate the entire loop when
NDEBUGis defined (I’ve just tested mine, and it does do that).Alternatively, you could surround the entire loop with
#ifndef NDEBUG/#endif. You say this “would defeat the purpose ofassertin the first place”, but I don’t really follow the reasoning.