If you are looking for the decompiler itself, visit https://github.com/jindrapetrik/jpexs-decompiler
NEW : We have got a new blog where we post some interesting SWF internals info.
List of issues#323 The default case of switch statement vanish in decompiled result
Author: 
freddie
freddieDate created:
Type: bug
Visibility: Everybody
Assigned to:
Labels: AS3
State: closed 
> What steps will reproduce the problem?
Decompile file: TestFfDec.swf
Result of class to check: Test
Method to check: function test03()
> What is the expected output? What do you see instead?
EXPECTED:
---------------------------------------
public function test03(b:Boolean) : void {
switch(this.memberVar1)
{
case 43:
case 45:
this.supportMethod2(this.supportMethod1(),this.supportMethod1(),b);
break;
default:
if (memberVar1 < 48 || this.memberVar1 > 57)
{
return;
}
this.supportMethod2(this.supportMethod1(), this.supportMethod1(), b);
break;
}
}
ACTUAL:
----------------------------------------------
private function test03(b:Boolean) : void {
switch(this.memberVar1)
{
case 43:
case 45:
this.supportMethod2(this.supportMethod1(),this.supportMethod1(),b);
break;
}
}
> What version of the product are you using? On what operating system?
1.7.0, Windows7x64
> Please provide any additional information below. Attach the file you have problem with
if necessary. If you do not want to publish files YOU CAN CHANGE VISIBILITY TO PRIVATE
Please see my attachments including the Flex source code and corresponding SWF
SomeUtilClass.as
State: new→opened
version 1.7.0u1 was released.
this should be fixed
State: opened→upgraded
No, this bug still can be reproduce in v1.7.0u1.
Please test it before release.
I can't reproduce it, too. I can see the default case in your attached example...And it
was fixed in a lot of places in my testfiles, too.
Still not fixed for me %)
I re-test again and found that the bug now can only be reproduced with "Automatic
deobfuscasion" unchecked. In the case of automatically deobfuscating, it can't.
By the way, I think the "Automatic deobfuscasion" shouldn't ON in dedault, because of in
real situation, almost SWFs are not compiled using a deobfuscator.
almost SWFs are not compiled using a deobfuscator.
--------------
i meant "obfuscator"
Please update status of this bug and the related changes log
You do not have to tell me to update issue status! I see you are not satisfied so it does
mean I have to work again on it. This issue does not have closed state yet, don't you
see?
I won't alter any changeslog! Changes log reflects changes made in the version in
question. "Fixed:" header does not necessarily mean the bug will not occur in the
feature.
Please take "New:" as "Feature" and "Fixed:" as "Bug" as this is how it meant to be -
issues which were changed, not issues which were closed.
You are taking it too literally.
State: upgraded→returned
This issue seems to be fixed in latest nightly.
State: returned→upgraded
I close this issue due to inactivity. Please create new issue if problem persists.
State: upgraded→closed