Comments on: Obscure AS3 for-switch-if-false bug (VerifyError)

By: asif shaik

asif shaik — Mon, 14 Nov 2011 09:31:45 +0000

Thanks a lot.It worked for me

By: Shubhra Bhushan

Shubhra Bhushan — Tue, 30 Aug 2011 10:26:40 +0000

Thanks a ton! You saved my day

By: Jon

Jon — Wed, 11 May 2011 16:20:48 +0000

I cant tell you how grateful I am that you posted this solution. I have been tearing my hair out over the past few days trying to find out why some users were getting unexplained errors, and other were not. Turn out it was directly as a result of this.

What a piece of shit Flex is. Thankfully I am moving on from it.

By: bemoo

bemoo — Tue, 29 Mar 2011 00:29:21 +0000

tq tq tq tq tq…
because it has solve my problem..

By: TomG

TomG — Wed, 23 Mar 2011 17:30:59 +0000

Thank you very much for this posting. I’d left out a break statement accidentally within a complicated set of loops/switches. The runtime error was ugly (class couldn’t reconcile with class). This was EXACTLY the problem. It would have been a long hard day if I had not seen this posting!

By: GF87

GF87 — Sun, 16 Jan 2011 19:02:31 +0000

I’m pretty sure you just saved my day!

Thanks!!!

By: jack

jack — Sat, 18 Dec 2010 02:04:05 +0000

I believe that is indeed invalid syntax. Break statements are scoped to the iterator scope they exist within. The break is bound to the switch. Case statements execute everything after them until they reach a beak or default statement. While looping through the Object’s properties, it has to call the switch and test against every prop against case. As there is no statement following case, which requires a statement, there is no end to the line to move onto the next execution instruction. You just hang and error out. I bet null; in the if statement won’t throw the error.

By: Mark

Mark — Tue, 19 Oct 2010 00:59:49 +0000

Thanks!

By: Ray Birk

Ray Birk — Sat, 16 Oct 2010 01:17:19 +0000

Thanks! Looks like the problem is fixed in Flash player 10.1 btw.

By: John

John — Mon, 11 Oct 2010 15:47:08 +0000

it seems that putting an

else ;

behind the code as in

switch (’s’) {
case ’s’:
if (null)
{
break;
}
else ;
}

also fixes this bug.