[mtasc] more feedback and private acesss specifier question
ncannasse at motion-twin.com
Fri Dec 10 14:07:53 CET 2004
> 1. Shorcut constructor syntax, new Foo; for creating a new instance
> without arguments should be allowed. Currently MTASC shows the error
> "parse error Unexpected ;".
New is a constructor call, parenthesis should be mandadory. The fact that
they're optionnal for MMC is simply bad.
> 2. When using -pack with packages that are non existent MTASC does not
> throw any error.
> mtasc -cp "F:\flash\classLibrary" -pack org/nosuchpackage -swf
> test.swf -header 400:400:31
> I think an explicit error should be thrown here.
What if the package is empty ? or does not contains any .as file ?
I prefer to let the user take care of checking that he's calling the good
executable with the good parameters.
> 3. For classes with no super class or those extending Object,
> super.methodName () seems to stall the compiler unexpectedly.
> 4. With the MMC the private access specifier actually acts like the
> protected access specifier of java. What does the private access
> specifier of MTASC relate to. The reason i ask is, i am trying to do
> super.methodname calls on private methods which gives the error, "type
> error Cannot access private field doFoo".
I'll have a look at that and fix it.
More information about the mtasc