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 talked about class
loading.

So... I still need to know how I should do this (accessors).

Mainly this took me 1 hour so it just got me into the AST better, it's been
a while.

Mike


On Fri, May 29, 2015 at 4:58 PM, Alex Harui <aha...@adobe.com> wrote:

> 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" <teotigraphix...@gmail.com> wrote:
>
> >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
> >    {
> >        _property = value;
> >    }
> >
> >    public function ClassA()
> >    {
> >    }
> >
> >    public function showValue():void
> >    {
> >        Window.alert(_property);
> >    }
> >}
> >}
> >
> >
> >Mike
> >
> >
> >
> >
> >
> >On Fri, May 29, 2015 at 4:31 PM, Michael Schmalle
> ><teotigraphix...@gmail.com
> >> wrote:
> >
> >> 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 this output from the
> >> previous I showed with TypeScript output.
> >>
> >> So it seems baring all the stuff that comes with this, we have a couple
> >> options which will need to be hashed out later about "what" is going to
> >>be
> >> output.
> >>
> >> These emitters can easily be configured, so we can have different types
> >>of
> >> output for people's use cases.
> >>
> >> var ClassA = (function () {
> >>     function ClassA() {
> >>         _classCallCheck(this, ClassA);
> >>
> >>         this._property = "init";
> >>     }
> >>
> >>     _createClass(ClassA, [
> >>         {
> >>         key: "property",
> >>         get: function () {
> >>             return this._property;
> >>         },
> >>         ",
> >>         set: function (value) {
> >>             this._property = value;
> >>         }
> >>         },
> >>         {
> >>         key: "showValue",
> >>         value: function showValue() {
> >>             alert(this._property);
> >>         }
> >>         }
> >>
> >>     ]);
> >> })();
> >>
> >> Mike
> >>
>
>

Reply via email to