Commenting out isXMLish fixes the errors related to the XML and XMLList classes.
I just committed my current code which compiles with no errors. (Yay!) I’ll probably work on fixing some more holes in the XML classes today/tomorrow and try to cross-compile some code early next week. I feels like we’ve made some great progress on this. It’s going to be very exciting when this works! Harbs On Feb 17, 2016, at 9:41 AM, Alex Harui <aha...@adobe.com> wrote: > Re #2, in Falcon's org.apache.flex.compiler.internal.tree.as.IdentifierNode, > try commenting out around line #845: > > if (isXMLish(baseType, project)) > return null; > > If that makes it work better, we might add a compile flag to neuter > isXMLish(). > > Re #1: This looks like a parser problem which usually takes more than one day > to fix so I'll have to work on it tomorrow. > > Regarding testing, I would write a test app in the manualtests folder like > the ReflectionTest > > HTH, > -Alex > > > From: Harbs <harbs.li...@gmail.com> > Date: Tuesday, February 16, 2016 at 10:32 PM > To: Alex Harui <aha...@adobe.com> > Subject: Re: [FALCONJX][FLEXJS] More XML handling > > Yes. I committed everything last night. > > On Feb 16, 2016, at 11:27 PM, Alex Harui <aha...@adobe.com> wrote: > >> If you have committed everything I will take a look later. >> >> Sent from my LG G3, an AT&T 4G LTE smartphone >> >> ------ Original message------ >> From: Harbs >> Date: Tue, Feb 16, 2016 1:13 PM >> To: dev@flex.apache.org; >> Subject:Re: [FALCONJX][FLEXJS] More XML handling >> >> I’m done for the day. I fixed most of the errors I understand. >> >> If someone could give me direction with these two issues, that would be >> great. >> >> Tomorrow, I plan to fix some of the holes that I left. Once I do that, I am >> going to see if I can figure out if I can use this to cross-compile some >> simple AS code using XML. I’m not quite sure I understand how to go about it >> but we’ll see… >> >> Harbs >> >> On Feb 16, 2016, at 9:36 PM, Harbs <harbs.li...@gmail.com> wrote: >> >> > I created a new target: >> > <target name="asjs" >> > depends="check-falcon-home,check-falconjx-home,more-props,compile-asjs"> >> > </target> >> > >> > You can see the full gamut of errors here: http://pastebin.com/UzBUFtQY >> > >> > I’ve fixed some, but there are still some legitimate errors there. >> > However, the vast majority are the errors I was talking about. >> > >> > On Feb 16, 2016, at 8:42 PM, Alex Harui <aha...@adobe.com> wrote: >> > >> >> You might try disabling the compile target and only use compile-asjs. It >> >> should avoid playerglobal and have fewer conflicts. Please post code >> >> snippets for errors you are getting. >> >> >> >> Sent from my LG G3, an AT&T 4G LTE smartphone >> >> >> >> ------ Original message------ >> >> From: Harbs >> >> Date: Tue, Feb 16, 2016 10:24 AM >> >> To: dev@flex.apache.org; >> >> Subject:[FALCONJX][FLEXJS] More XML handling >> >> >> >> Starting a new thread because the last one was getting kind of long… >> >> >> >> I started fixing some of the compile errors in XML, but there are two >> >> problems I don’t know what to do with: >> >> >> >> 1. Object.defineProperty: The compiler is complaining that get and set >> >> are not allowed. I’m not sure if I did something wrong, or there’s a real >> >> problem here. (I commented out the defineProperty in XML, but left in the >> >> XMLList ones.) >> >> 2. I’m getting lots of complaints about properties not being available >> >> for XML and XMLList. It looks like the compiler thinks that we’re using >> >> the default ActionScript classes instead of the new JS-only classes. I’m >> >> not sure if the build file needs to be re-worked or what. I’m not sure >> >> how to go about differentiating to the compiler between the different >> >> classes. >> >> >> >> If our compiler experts can point me in the right direction here, that >> >> would be great. >> >> >> >> Harbs >> > >
