Loop condition: why “not-equal” instead of “lower-than”

Question

I was assigned to work on an Android-Java (real-time game) project with a considerable (partially legacy) code base.

Most of the loops I see are like this (where mjk

Answer 1

I remember encountering this quite a long time ago when coding c++.

The argument in its favour was that the value of i on exiting the loop was clearer - i.e. it was clear at a glance that on loop exit i would == count.