http://guyinthechair.com //the blog of Paul Taylor Fri, 18 Nov 2011 01:22:46 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 http://guyinthechair.com/2009/01/flex-3-debugger-anomaly/ http://guyinthechair.com/2009/01/flex-3-debugger-anomaly/#comments Fri, 02 Jan 2009 20:36:45 +0000 Paul Taylor http://guyinthechair.com/?p=11 Working today, I discovered the debugger does something silly with for loops. If you have code formatted like so:

var i:int = 0;
var foo:int = 3;
for(; i < foo; i++){
        //Code here
}

If you set a breakpoint on line 3, where the for loop is defined, the Flex debugger will only stop after it has been through one iteration of the loop. This caught me off guard, and for a minute I thought it was immediately incrementing the iterator. Only when I breakpointed on both the line of the for loop and on the first line inside my loop did I realize what was happening. The debugger stopped on the first line of my loop, not when it executed the condition the first time. This does not seem like standard debugger behavior at all. Does this happen to everyone? I know if you define the iterator inline, the debugger stops. Huh.

]]> http://guyinthechair.com/2009/01/flex-3-debugger-anomaly/feed/ 0