it is visible to code in all classes defined in the unnamed package, and so either shadows outer bindings named 'init' or masks mis-spellings of 'init'. An obvious solution is to put 'init' into a hidden namespace, but there are probably others that should be considered (like restructuring the code to avoid the need for a static method for initialization). Jd

This has a bit of impact on Flash Builder users -- whenever they bring up code hints for "this" for any class, they will see init() as one of the possible completions, even if the class doesn't have an init() function; this is potentially a little confusing.

Krzysztof was bitten by this on Friday. He had some code that looked something like this (this is from memory): // init.as package { public namespace init = "http://example.com"; } // MyClass.as package { public class MyClass { use namespace init; .... public function foo():void { foo.init::bar = 3; } } } He kept getting strange compile-time error messages; when I took a look, I remembered this bug, and told him to rename his namespace "init" to something else, and that fixed it.

Versioning will fix this.

Simplest test case - this should print 'undefined': package { print(Object.init); }

Not for review yet, but once bug #559994 lands this will be roughly the right fix for the present bug.

confirmed fixed