Hi Alex,
> For me, when I compile a FlexJS example like FlexJSStore, addDependency is
> called quite often while servicing “handleSyntaxTreeRequest” before any
> walking of the AST. I wonder if there is something different about the
> way you are compiling this code you are working on.
I hadn't a lot and didn't want to spend more time on this issue until today,
guess why :-)
Anyway, if I call COMPJSC directly I haven't this issue, so, I will hopefully
find out why quickly now.
One thing I discovered though is that with Falcon, the combination of getter /
setter for a same function at package level is not supported (the legacy
compiler support it):
package goog.events {
public function get fireListener():Function{return null;}
public function set fireListener(value:Function):void{}
}
Error: An externally-visible definition with the name
'goog.events.fireListener' was unexpectedly found.
Can you take care of it or drive me into fixing it ?
Thanks,
Frédéric THOMAS
> From: [email protected]
> To: [email protected]
> Subject: Re: [FlexJS] Framework using externs (was: Setup Error)
> Date: Mon, 24 Aug 2015 16:28:37 +0000
>
>
>
> On 8/24/15, 8:07 AM, "Frédéric THOMAS" <[email protected]> wrote:
>
> >
> >
> >
> >> I’d have to dig into it, but yes, I think addDependency gets called
> >>quite
> >> often before we start walking the tree. But once you asked the
> >>question,
> >> it did occur to me that we do call into the resolving code during the
> >> walk, but I don’t know if that also results in addDependency.
> >
> >Not sure I understood everything but I can't see any call before walking
> >the tree to FlexJSProject.addDependency() which is the function used to
> >fill the requires that are then wrote in PackageHeaderEmitter using
> >FlexJSProject.getRequires(), is there a function supposed to store the
> >library definitions before the walk ?
>
> For me, when I compile a FlexJS example like FlexJSStore, addDependency is
> called quite often while servicing “handleSyntaxTreeRequest” before any
> walking of the AST. I wonder if there is something different about the
> way you are compiling this code you are working on.
>
> -Alex
>
>
