MTASC more strict than Macromedia compiler?

[Ivan-64]

Some parts of this message have been removed. Learn more about Nabble's security policy.

I am new to Flash development.  Technically, I should not be doing any Flash development, all I need to do is change some ActionScript given to me by a third-party.
 
My hope was to simply edit the .as files and compile with MTASC since I do not have the Flash IDE.  I do not need to edit the .fla files.  When compiling with MTASC, I would receive several compilation errors.  I thought this behavior was strange since I have given this third-party code to a front-end Flash developer, and he had no problems.  I then loaded the code into a computer with Macromedia Flash, and the code compiled fine.
 
The problem is not with MTASC since the errors discovered were truly errors.  It appears Macromedia Flash is not as strict when it comes to compilation.  A few errors were:
 
* Using the equality instead of the assignment operator:
    if (a==b) {
        c == 1;      // ERROR! should be = not ==
    }
 
* Undefined variables:
    for (var i:Number = 0;i < someArray.length;i++)
        {
            if (isNaN(num)) continue;         // ERROR num not defined
            someArray[i] = num;
        }
 
* Type error Cannot access member variable FOO in static function
 
What gives?  Can I get MTASC to be more forgiving?  The ultimate goal will be to have the fla and as files in a repository and create SWF files from a build tool, without ever needing Flash (except when editing fla files).
 
Cheers,
 
Ivan
 

---

Windows Live™ Hotmail®: Chat. Store. Share. Do more with mail. See how it works.
--
MTASC : no more coffee break while compiling