this pattern is structured to avoid the use of an additional stack (local) variable to track a condition, and to skip superfluous execution of code once that co

this pattern is structured to avoid the use of an additional stack (local) variable to track a condition, and to skip superfluous execution of code once that condition is detected. i've used it myself to optimize inner loops of very simple un-accelerated graphics rendering code (which sped it up considerably, since it is potentially skipping many levels of unnecessary execution on the cpu, millions of times), but i agree with some posters here, using it in a security context like this is a bit daring. still, having said that, this bug really is an indictment of the testing process and not really bad style per se.