Static field initializers are improperly flagged as errors

[Nypyren]

For example:

public class ClassName
{
    private static var m_array:Array = new Array();
   
    m_array["name1"] = "ASDF";  // This is flagged as an error, but is legal in AS3.
}

This also occurs with non-array types like ints, strings, etc.

[Dermot]

Thanks for reporting this - it is a bug.

It won't stop a build since, as you point out, this is correct ActionScript syntax.

We've fixed this in the latest build of Amethyst 1.6 which should be available early next week.

We'll post here when it's ready with a download link so you can try it.

Dermot

[Dermot]

Fixed in 1.6.0 build 1375 (http://sapphiresteel.com/forum/index.php?topic=785.0)

Dermot

[Nypyren]

Excellent, thanks!

[Nypyren]

I just found a second bug in the static field initializers:  If we're assigning a classname to a variable, the intellisense scanner thinks it's an error.

Example:

protected static var m_classMap:Array= new Array();
m_classMap["A"] = ClassA; // where these are names of classes
m_classMap["B"] = ClassB;
m_classMap["C"] = ClassC;


This assignment gets scanned properly in a function body, but not out in the class body.

[Dermot]

yes - you are quite right.  A class name is statically known at that point, so it can be an rvalue in that context.

We'll upload a new version with a fix later in the week (give you a chance to find any more errors!)

Dermot