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 see somewhere it mentions:
for ( itr = files.begin(); itr < files.end(); ++itr ) // WRONG
for ( itr = files.begin(); itr != files.end(); ++itr ) // ok
Why is the first expression wrong? I always used the first expression, and didn’t have any problems.
Ordering comparisons such as
<,>,<=,>=will work for random-access iterators, but many other iterators (such as bidirectional iterators on linked lists) only support equality testing (==and!=). By using!=you can later replace the container without needing to change as much code, and this is especially important for template code which needs to work with many different container types.