On 5/29/15, 2:11 PM, "Michael Schmalle" wrote:
>Yeah it is but we were talking about property super calls and this was
>brought up.
>
>Alex, understand I am ignorant here with js. I probably have 100+ emails
>now pleading for somebody to tell me how I should emitter super calls to
>properties.
Yeah it is but we were talking about property super calls and this was
brought up.
Alex, understand I am ignorant here with js. I probably have 100+ emails
now pleading for somebody to tell me how I should emitter super calls to
properties.
Josh wasn't keen on the whole GCC dependency but we then
Maybe I’m not understanding, but the output didn’t look like JS to me. It
looked like data that goes into some _createClass abstraction. Which is
fine, but a bit spooky if we want to claim “vanilla”.
-Alex
On 5/29/15, 1:39 PM, "Michael Schmalle" wrote:
>Oh yeah, the .as for this is;
>
>
>
>pa
Oh yeah, the .as for this is;
package com.model
{
import randori.webkit.page.Window;
public class ClassA
{
private var _property:String = "init";
public function get property():String
{
return _property;
}
public function set property(value:String):void
{
Hi,
I have been throwing stuff at the wall today and one thing I wanted a POC
of is the output of Babble since it "seems" to have an implementation of
super accessor calls.
So using the same JXEmitter, I have composed sub emitters and I have only
overridden 2 (ClassEmitter, MethodEmitter) to get
