Hehe well perhaps obvious was a bit presumptuous of me? But really it seemed like the only course of action. I’m not entirely sure how one would identify break points? The analyzer is aimed...

Hey guys, I'm creating a code analyzer that enforces the CamelCase convention that Java uses, for example, thisIsAWellConstructedJavaVariable and thisinnotawellconstructedjavavariable.

So...

I've never really heard of optimization on a high level programming language. In assembly perhaps.
So I would expect that X = 0 is more efficent that X = Y * 0;
The issue lies with memory access...