Skip to main content
Participating Frequently
April 26, 2013
Question

AIRSDK Compiler not finding errors

  • April 26, 2013
  • 2 replies
  • 695 views

I am having problems with the new ASC 2.0 compiler in the AIRSDK not finding obvious errors during compilation, leading to runtime errors.  I am using AIRSDK 3.7.

Here is one example that fails:

SomethingBase.as:

package

{

          public class SomethingBase

          {

                    public function twoargs(a : *, b : *) : void

                    {

                    }

          }

}

SomethingElse.as:

package

{

     public class SomethingHere extends SomethingBase

          {

                    public function SomethingHere()

                    {

                              super();

                    }

                    override public function twoargs(a : *, b : *) : void

                    {

                              super.twoargs();

                    }

          }

}

No errors are generated in FlashBuilder 4.7, although a runtime error occurs when this code executes.  This occurs when the project type is ActionScript Library or ActionScript Project.  If the project type is 'Flex Library' or 'Flex Application', compiled with Apache Flex 4.9.1, the expected compiler error appears: "

DescriptionResourcePathLocationType
1136: Incorrect number of arguments.  Expected 2.SomethingElse.as/xxx-flexlib/srcline 13Flex Problem

AIRSDK compiler also fails to warn from the command line:

> /Applications/Adobe\ Flash\ Builder\ 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK/bin/compc -source-path . -include-sources . -output blah.swc

Using AIR SDK: /Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK

Loading configuration: /Applications/Adobe Flash Builder 4.7/eclipse/plugins/com.adobe.flash.compiler_4.7.0.349722/AIRSDK/frameworks/flex-config.xml

1826 bytes written to /<REDACTED>/blah.swc in 0.830 seconds

This topic has been closed for replies.

2 replies

chris.campbell
Legend
April 27, 2013

Could you please open a bug report on this over at bugbase.adobe.com?  Once added, please let me know the bug number and I'll follow up internally.

Thanks,

Chris

Participating Frequently
April 30, 2013

FWIW this also happens with all calls made through an interface.  The compiler seems to be treating super. and someinterface. as like calling through *.