I've been meaning to create a JIRA issue for another MXML parsing issue that I recently discovered.
If you have an un-closed XML comment <!--, the compiler will get stuck in an infinite loop. Similarly, if you have <fx:Script><![CDATA[ and it is only closed with </fx:Script> (without the closing ]]> for the CDATA), the compiler will also get stuck in an infinite loop. I discovered these while testing my VSCode extension, and the compiler JAR was in memory rather than executed from the command line. I haven't tried it from the command line yet to see if the behavior is the same or not. I was planning to do that final test before opening the issue, but this topic seems related, so I thought I'd bring it up now. - Josh On Tue, Nov 22, 2016 at 11:19 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 11/22/16, 2:40 AM, "Harbs" <harbs.li...@gmail.com> wrote: > > > >There’s not a lot in the project. Please take a look and let me know if > >you can spot what’s wrong. > > I don't know if this is the only problem, but I did find a problem that I > should have seen earlier, but I only saw after spending an hour stepping > through the debugger. Check out the last line of your MXML file. It is: > > <js:Application> > > > I haven't changed your code yet since I want to see why the compiler did > not report an error. But for sure, that's not right. It's amazing that > we both did not see this earlier. ROFL! > > -Alex > >
