break and continue about gmqcc HOT 3 CLOSED

I was never a fan of the complex control structures involved with break and continue. They pose problems for static analysis because it isn't easy (or rather is impossible) to linearize, you need extensive simulation with constant propagation of loop structures (which might not be possible is the variables are not constant). Opposed to goto which is just single statement that doesn't involve structural semantics. I would generally advise against them in actual code, since they are actually a rather contributing factor to broken code. I think if you implement them, to consider giving them stricter semantics, i.e nested break/continue simply spitting a warning (unless it's an explicit multiscope statement like break this; where this can be a scoped-label). I would like to think of a better solution for all of this though, something that can be statically analyzed. If that is possible? Perhaps I'm just being picky.

from gmqcc.

Regular non-labeled variants are in now.

from gmqcc.

testcases added and succeeding

from gmqcc.