Harbs

FWIW, here's an implementation in Spectrum: https://unhurdle.github.io/spectrum-royale/#!splitview https://github.com/unhurdle/spectrum-royale/blob/master/Spectrum/src/com/unhurdle/spectrum/VSplitView.as

The compiler is probably failing to add double backslashes somewhere. The bane of string parsing... ;) This bug probably belongs in https://github.com/apache/royale-compiler/

Tough one. The ecma spec is that has `hasOwnProperty` does not return true for inherited properties. I think the Flash behavior is different. I'm loath to just mimic the Flash...

Yeah. This is a known problem. Currently it's only possible to reliably use native types in static initializers. Static initializers are evaluated when the JS file loads. The only way...

Actually, it looks like this is a global problem. I just picked EdgeData (because it's a simple class) and added `this.bottom()` in the constructor and no error. If I add...

@aharui I originally agreed with your position, but I've bumped into lots of weird bugs due to booleans not being initialized. That includes "undefined" ending up in some of my...

> `b.c=0;` // b is 'a.prototype' I assume you mean `b.c=!1` It's not just `==`. You'd also need to do `bool1 = !!bool2` for every single assignment because you never...

As a point of reference, I just audited *all* of the Royale framework code. There's 1264 public, private and protected boolean variables declared across all the frameworks combined and this...

> Also, again fwiw, I think jx-compiler should not try to output things like **!!0** or **!0** etc here... it should be **true** or **false**. GCC does all that stuff...

> I seem to recall a discussion on another topic where we were going to leave an option on by default but keep it off in the framework. I'm fine...