Hi Mike,
sorry if I confused you, the Wiki page is still work in progress and much
my "brain dump" of all AS3 features I know have to be simulated, and also
how I'd suggest to do so.
As I continue, I'm going to add more illustrating examples. Concerning the
private members, I think you are on the right track. The "class inheritance
level" I am talking about is an optimization over using the fully qualified
name of the class as postfix for private fields. In Jangaroo, we compute
the inheritance level (or depth) of the class and simply use that number.
This also ensures unique identifiers, as a class can never have the same
inheritance level as any super or sub class.
Greetings
-Frank-
On Mon, Dec 31, 2012 at 1:35 PM, Michael Schmalle
<apa...@teotigraphix.com>wrote:
> Hey Frank,
>
> I'm getting a bit confused here. I guess I really need to spend some time
> and get the relevant javascript information under my belt.
>
> Is what you are showing on this page, your solution?
>
> Please comment on the below if the code is what you are talking about in
> those paragraphs;
>
>
> Members and visibility
> ---------------------------
>
> private function _privateMethod():void {
> }
> - this._privateMethod()
>
> public var foo:int;
> - foo = 42
>
> private var foo:int;
> - foo$FooClass = 42
>
> internal bar:int;
> - bar$foo_bar_baz
>
> The above seems like it's going to be pretty universal regardless of what
> production scheme we use. Is there any articles you know about that explain
> JS scope and how it's implemented? Or is that just the ECMA5 specs?
>
> Mike
>
>
>
>
>
>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>
>
