HI, well I'm not talking about taking EXTERNC out of compiler.jx into a dedicated, package. I'm talking about taking the Integration-Tests that rely on parts of compiler.jx being built into a dedicated testsuite artifact. I think EXTERNC is ok to be kept where it is.
I am worried about yet another tool that has to be installed, yet another packaging system and all the integration problems that come with it. I would probably be able to integrate things into the Maven build, but we are not making things simpler but adding another technology stack for creating simple AS code. I think it should be easier to crate such a generator using a JavaScript grammar and Antlr4. But I would really like to start working on something like this AFTER finishing the migration to Maven. Otherwise it's shooting on moving targets. Chris ________________________________________ Von: Michael Schmalle <teotigraphix...@gmail.com> Gesendet: Montag, 14. März 2016 18:02 An: dev@flex.apache.org Betreff: Re: AW: AW: AW: AW: AW: AW: AW: LAST CALL] Release FlexJS/FalconJX 0.6.0 Yeah lets not get started on the whole parsing js files. :) What I liked about gcc is it abstracted the AST and took care of the parsing irregularities of JS. The problem is the AST walking like I did in ExternC, I had to template that as though I knew I was parsing prototypes as the extern definition says. It also relies on jsdoc tags so add another layer. JS is just a pain in the ass to deal with, plain and simple. Years ago I was able create a grammar, parser and a read/write framework for ActionScript using ANTLR only because it closely followed a spec, I hate JS for this reason. :) I just hate duplicating work and that is why I asked Josh what I did, I totally wasn't asking him to donate anything. Mike On Mon, Mar 14, 2016 at 12:13 PM, Alex Harui <aha...@adobe.com> wrote: > > > On 3/14/16, 8:34 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote: > > >On Mon, Mar 14, 2016 at 11:29 AM, Alex Harui <aha...@adobe.com> wrote: > > > >> > >> > >> On 3/14/16, 8:19 AM, "Michael Schmalle" <teotigraphix...@gmail.com> > >>wrote: > >> > >> >That said, there is only "so much" that compiler can do because I > >>hacked > >> >it > >> >together in about a month. Thinking about a way to create something > >>that > >> >can support a yriad amount of definitions that are supported by the > >> >current > >> >TS community is definitely something to think about. > >> > >> Yes, but when last discussed, Justin called the licensing integrity of > >>the > >> TS files into question, so it may be less work for us to have any code > >> that generates extern SWCs from those files come from a non-Apache > >>project > >> unless someone wants to take the time to sort through it all. Of course > >> Apache is interested in all sorts of things like dts2as to be > >>open-sourced > >> at Apache, but the reality is that it won't always be the case. > >> > >> > >Yeah, Yeah yeah :) I remember that conversation and that is why I made the > >compiler. But, I forgot that it was never resolved. > > It is really up to Josh as to whether he wants to bring dts2as to Apache. > He has every right to keep it outside of Apache and maybe even make some > money off of it. > > > > >Ok I ask this, is there anything it doesn't do right now for the core > >stuff > >you are working? > > Are you asking about ExternC? It works well enough for good extern .js > files. The problem is that there are a few libraries (Google Closure > Library and CreateJS and probably Cordova) were there is no externs files > so we are asking ExternC to try to process the actual code, which it > doesn't do so well, so we've fashioned other ways of skipping ExternC or > batch modification of the .js files to get ExternC to work and that is > making more work for Chris' Maven stuff since the 8 SWCs have at least 3 > or 4 different recipes. > > IMO, it would be awesome to see ExternC grow into a tool that could > generate the SWCs from the actual library code so folks don't have to > maintain d.ts files or extern .js files, but I think that's a ton of work > especially given that some JS libraries are written with different JS > patters like the IIFE pattern. > > Also, Chris and I are wondering if ExternC could be its own folder like > compiler and compiler.jx. It might simplify the Maven work. > > -Alex > > >
