A student's question

My teacher keeps drilling into our collective heads that using the break command is harmful, and that if we wish to terminate a loop early it would be far better to create a boolean variable, set it to 0, and add a condition to the head of the loop, and set the boolean variable to 1 when a break is needed. Note that this way you actually have to check this every single loop (where it is not needed almost every time) as well as waste a command to reset the boolean in case it was set to true.

Is there a reason to this?

>>1
Your teacher is a idiot. Let's say I have a Devyrish piece of code that determines if a number is prime..

boolean isPrime = true;

for (int divisor = 2; divisor <= number/2 && isPrime; divisor++) {
  if (number % divisor == 0) {
    isPrime = false:
  }
}

Now let's say I wanna be like the SICP fags that roam this joint and abstract this loop. What do I abstract? Divisor or isPrime?

The answer becomes a bit clearer if I would re-write this loop using a break statement.